diff options
| author | Roland Dreier <rolandd@cisco.com> | 2008-06-09 09:58:42 -0700 |
|---|---|---|
| committer | Roland Dreier <rolandd@cisco.com> | 2008-06-09 09:58:42 -0700 |
| commit | 4c0283fc561d79a4f94ab48ec37282e15273d1f8 (patch) | |
| tree | 2826dd873ca2e9ce699c11211582f2f9425871e4 /include/rdma | |
| parent | 8079ffa0e18baaf2940e52e0c118eef420a473a4 (diff) | |
| download | kernel-crypto-4c0283fc561d79a4f94ab48ec37282e15273d1f8.tar.gz kernel-crypto-4c0283fc561d79a4f94ab48ec37282e15273d1f8.tar.xz kernel-crypto-4c0283fc561d79a4f94ab48ec37282e15273d1f8.zip | |
IB/core: Remove IB_DEVICE_SEND_W_INV capability flag
In 2.6.26, we added some support for send with invalidate work
requests, including a device capability flag to indicate whether a
device supports such requests. However, the support was incomplete:
the completion structure was not extended with a field for the key
contained in incoming send with invalidate requests.
Full support for memory management extensions (send with invalidate,
local invalidate, fast register through a send queue, etc) is planned
for 2.6.27. Since send with invalidate is not very useful by itself,
just remove the IB_DEVICE_SEND_W_INV bit before the 2.6.26 final
release; we will add an IB_DEVICE_MEM_MGT_EXTENSIONS bit in 2.6.27,
which makes things simpler for applications, since they will not have
quite as confusing an array of fine-grained bits to check.
Signed-off-by: Roland Dreier <rolandd@cisco.com>
Diffstat (limited to 'include/rdma')
| -rw-r--r-- | include/rdma/ib_verbs.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/include/rdma/ib_verbs.h b/include/rdma/ib_verbs.h index 911a661b727..31d30b1852e 100644 --- a/include/rdma/ib_verbs.h +++ b/include/rdma/ib_verbs.h @@ -105,7 +105,6 @@ enum ib_device_cap_flags { */ IB_DEVICE_UD_IP_CSUM = (1<<18), IB_DEVICE_UD_TSO = (1<<19), - IB_DEVICE_SEND_W_INV = (1<<21), }; enum ib_atomic_cap { |