summaryrefslogtreecommitdiff
path: root/include/rxrpc
diff options
context:
space:
mode:
authorJianxin Xiong <jianxin.xiong@intel.com>2016-07-25 20:38:25 (GMT)
committerDoug Ledford <dledford@redhat.com>2016-08-02 20:00:58 (GMT)
commitd9f8723924d5955979d05cb7f4f10d9ebac39b7d (patch)
treef48b2c3d7abd25c5a817fc262e9a788aeeb4eb21 /include/rxrpc
parente8f8b098a44a66d3da81e460aed465f26693e120 (diff)
downloadlinux-d9f8723924d5955979d05cb7f4f10d9ebac39b7d.tar.xz
IB/rdmavt: Handle local operations in post send
Some work requests are local operations, such as IB_WR_REG_MR and IB_WR_LOCAL_INV. They differ from non-local operations in that: (1) Local operations can be processed immediately without being posted to the send queue if neither fencing nor completion generation is needed. However, to ensure correct ordering, once a local operation is posted to the work queue due to fencing or completion requiement, all subsequent local operations must also be posted to the work queue until all the local operations on the work queue have completed. (2) Local operations don't send packets over the wire and thus don't need (and shouldn't update) the packet sequence numbers. Define a new a flag bit for the post send table to identify local operations. Add a new field to the QP structure to track the number of local operations on the send queue to determine if direct processing of new local operations should be enabled/disabled. Reviewed-by: Mike Marciniszyn <mike.marciniszyn@intel.com> Reviewed-by: Dennis Dalessandro <dennis.dalessandro@intel.com> Signed-off-by: Jianxin Xiong <jianxin.xiong@intel.com> Signed-off-by: Dennis Dalessandro <dennis.dalessandro@intel.com> Signed-off-by: Doug Ledford <dledford@redhat.com>
Diffstat (limited to 'include/rxrpc')
0 files changed, 0 insertions, 0 deletions