summaryrefslogtreecommitdiffstats
path: root/Documentation/oops-tracing.txt
diff options
context:
space:
mode:
authorRoland Dreier <rolandd@cisco.com>2008-06-09 09:58:42 -0700
committerRoland Dreier <rolandd@cisco.com>2008-06-09 09:58:42 -0700
commit4c0283fc561d79a4f94ab48ec37282e15273d1f8 (patch)
tree2826dd873ca2e9ce699c11211582f2f9425871e4 /Documentation/oops-tracing.txt
parent8079ffa0e18baaf2940e52e0c118eef420a473a4 (diff)
downloadtalos-obmc-linux-4c0283fc561d79a4f94ab48ec37282e15273d1f8.tar.gz
talos-obmc-linux-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 'Documentation/oops-tracing.txt')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud