On 28/10/2013 23:22, Hefty, Sean wrote:
Assuming that flags will be a bitwise OR of values, they should be an int, not
an enum.
Hi Sean, anything else from your side re the IB core patches and this
series in general?
Or.
--
To unsubscribe from this list: send the line unsubscribe
On 10/28/2013 11:22 PM, Hefty, Sean wrote:
+enum ib_mr_create_flags {
+ IB_MR_SIGNATURE_EN = 1,
+};
+
+/**
+ * ib_mr_init_attr - Memory region init attributes passed to routine
+ * ib_create_mr.
+ * @max_reg_descriptors: max number of registration units that
+ * may be used
Hi Sean, anything else from your side re the IB core patches and this
series in general?
Do we have a user of these changes?
--
To unsubscribe from this list: send the line unsubscribe linux-rdma in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Tue, Oct 29, 2013 at 9:34 PM, Hefty, Sean sean.he...@intel.com wrote:
Hi Sean, anything else from your side re the IB core patches and this
series in general?
Do we have a user of these changes?
Oh sure, we didn't do that just for the fun of it... Sagi is working
to enhance the upstream
This commit introduces verbs for creating/destoying memory
regions which will allow new types of memory key operations such
as protected memory registration.
Indirect memory registration is registering several (one
of more) pre-registered memory regions in a specific layout.
The Indirect region
+enum ib_mr_create_flags {
+ IB_MR_SIGNATURE_EN = 1,
+};
+
+/**
+ * ib_mr_init_attr - Memory region init attributes passed to routine
+ * ib_create_mr.
+ * @max_reg_descriptors: max number of registration units that
+ * may be used with UMR work requests.
+ * @flags: MR