diff options
| author | 2005-06-27 14:36:41 -0700 | |
|---|---|---|
| committer | 2005-06-27 15:11:45 -0700 | |
| commit | 34a4a753d15f905158d77fb81adc9c19a02a4639 (patch) | |
| tree | 73c0bacd8b57dcde4320ed4a89c2e22e07586c93 /tools/lib/python/kdoc/python_version.py | |
| parent | [PATCH] IB/mthca: Set QP static rate correctly (diff) | |
[PATCH] IB/mthca: Set RDMA/atomic capabilities correctly
mthca apparently had the meanings of the max_rd_atomic and max_dest_rd_atomic
QP attributes backwards. max_rd_atomic limits the maximum number of
outstanding RDMA/atomic requests as an initiator (on a send queue), and
max_dest_rd_atomic specifies the resources allocated to handle RMDA/atomic
requests from the remote end of the connection. We were programming our QP
context with these values swapped.
Signed-off-by: Roland Dreier <roland@topspin.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions
