On 10/22/2013 9:20 PM, Hefty, Sean wrote:
Would we lose anything making this a new operation for the QP, versus
trying to hook it into the existing ib_post_send call?
If I understand correctly you are suggesting making it a verb? Well this
operation is a fast-path operation - so I guess we
I don't think so,
Signature MR simply describes a signature associated memory region
i.e. it is a memory region that
also defines some signature operation offload aside from normal RDMA
(for example validate strip).
SGL are used to publish several rkeys for the server/target/peer to
Would we lose anything making this a new operation for the QP, versus
trying to hook it into the existing ib_post_send call?
If I understand correctly you are suggesting making it a verb? Well this
operation is a fast-path operation - so I guess we will loose it in this
case.
Take SCSI
The signature handover operation is binding all the necessary
information for the HCA together: where is the data (data_mr), where is
the protection information (prot_mr), what are the signature properties
(sig_attrs).
Once this step is taken (WR is posted), a single MR (sig_mr) describes
On 10/21/2013 5:34 PM, Hefty, Sean wrote:
The signature handover operation is binding all the necessary
information for the HCA together: where is the data (data_mr), where is
the protection information (prot_mr), what are the signature properties
(sig_attrs).
Once this step is taken (WR is
On 10/18/2013 1:51 AM, Hefty, Sean wrote:
@@ -885,6 +901,19 @@ struct ib_send_wr {
u32 rkey;
struct ib_mw_bind_info bind_info;
} bind_mw;
+ struct {
+ struct ib_sig_attrs
@@ -885,6 +901,19 @@ struct ib_send_wr {
u32 rkey;
struct ib_mw_bind_info bind_info;
} bind_mw;
+ struct {
+ struct ib_sig_attrs*sig_attrs;
+ struct ib_mr
