|
@@ -0,0 +1,85 @@
|
|
|
|
|
+/*
|
|
|
|
|
+ * Copyright(c) 2015 Intel Corporation.
|
|
|
|
|
+ *
|
|
|
|
|
+ * This file is provided under a dual BSD/GPLv2 license. When using or
|
|
|
|
|
+ * redistributing this file, you may do so under either license.
|
|
|
|
|
+ *
|
|
|
|
|
+ * GPL LICENSE SUMMARY
|
|
|
|
|
+ *
|
|
|
|
|
+ * This program is free software; you can redistribute it and/or modify
|
|
|
|
|
+ * it under the terms of version 2 of the GNU General Public License as
|
|
|
|
|
+ * published by the Free Software Foundation.
|
|
|
|
|
+ *
|
|
|
|
|
+ * This program is distributed in the hope that it will be useful, but
|
|
|
|
|
+ * WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
|
+ * General Public License for more details.
|
|
|
|
|
+ *
|
|
|
|
|
+ * BSD LICENSE
|
|
|
|
|
+ *
|
|
|
|
|
+ * Redistribution and use in source and binary forms, with or without
|
|
|
|
|
+ * modification, are permitted provided that the following conditions
|
|
|
|
|
+ * are met:
|
|
|
|
|
+ *
|
|
|
|
|
+ * - Redistributions of source code must retain the above copyright
|
|
|
|
|
+ * notice, this list of conditions and the following disclaimer.
|
|
|
|
|
+ * - Redistributions in binary form must reproduce the above copyright
|
|
|
|
|
+ * notice, this list of conditions and the following disclaimer in
|
|
|
|
|
+ * the documentation and/or other materials provided with the
|
|
|
|
|
+ * distribution.
|
|
|
|
|
+ * - Neither the name of Intel Corporation nor the names of its
|
|
|
|
|
+ * contributors may be used to endorse or promote products derived
|
|
|
|
|
+ * from this software without specific prior written permission.
|
|
|
|
|
+ *
|
|
|
|
|
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
|
|
|
|
+ * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
|
|
|
|
+ * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
|
|
|
|
|
+ * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
|
|
|
|
|
+ * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
|
|
|
|
+ * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
|
|
|
|
|
+ * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
|
|
|
|
+ * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
|
|
|
|
+ * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
|
|
|
|
+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
|
|
|
|
|
+ * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
|
+ *
|
|
|
|
|
+ */
|
|
|
|
|
+
|
|
|
|
|
+#include "mad.h"
|
|
|
|
|
+
|
|
|
|
|
+/**
|
|
|
|
|
+ * rvt_process_mad - process an incoming MAD packet
|
|
|
|
|
+ * @ibdev: the infiniband device this packet came in on
|
|
|
|
|
+ * @mad_flags: MAD flags
|
|
|
|
|
+ * @port: the port number this packet came in on
|
|
|
|
|
+ * @in_wc: the work completion entry for this packet
|
|
|
|
|
+ * @in_grh: the global route header for this packet
|
|
|
|
|
+ * @in_mad: the incoming MAD
|
|
|
|
|
+ * @out_mad: any outgoing MAD reply
|
|
|
|
|
+ *
|
|
|
|
|
+ * Returns IB_MAD_RESULT_SUCCESS if this is a MAD that we are not
|
|
|
|
|
+ * interested in processing.
|
|
|
|
|
+ *
|
|
|
|
|
+ * Note that the verbs framework has already done the MAD sanity checks,
|
|
|
|
|
+ * and hop count/pointer updating for IB_MGMT_CLASS_SUBN_DIRECTED_ROUTE
|
|
|
|
|
+ * MADs.
|
|
|
|
|
+ *
|
|
|
|
|
+ * This is called by the ib_mad module.
|
|
|
|
|
+ */
|
|
|
|
|
+int rvt_process_mad(struct ib_device *ibdev, int mad_flags, u8 port,
|
|
|
|
|
+ const struct ib_wc *in_wc, const struct ib_grh *in_grh,
|
|
|
|
|
+ const struct ib_mad_hdr *in, size_t in_mad_size,
|
|
|
|
|
+ struct ib_mad_hdr *out, size_t *out_mad_size,
|
|
|
|
|
+ u16 *out_mad_pkey_index)
|
|
|
|
|
+{
|
|
|
|
|
+ /*
|
|
|
|
|
+ * Drivers will need to provide a number of things. For exmaple counters
|
|
|
|
|
+ * will need to be maintained by the driver but shoud live in the rvt
|
|
|
|
|
+ * structure. More study will be needed to finalize the interface
|
|
|
|
|
+ * between drivers and rvt for mad packets.
|
|
|
|
|
+ *
|
|
|
|
|
+ *VT-DRIVER-API: ????
|
|
|
|
|
+ *
|
|
|
|
|
+ */
|
|
|
|
|
+ return IB_MAD_RESULT_FAILURE;
|
|
|
|
|
+}
|