Roland Dreier 1f71f50342 RDMA/cxgb3: Program hardware IRD with correct value ... Because of a typo in iwch_accept_cr(), the cxgb3 connection handling code programs the hardware IRD (incoming RDMA read queue depth) with the value that is passed in for the ORD (outgoing RDMA read queue depth). In particular this means that if an application passes in IRD > 0 and ORD = 0 (which is a completely sane and valid thing to do for an app that expects only incoming RDMA read requests), then the hardware will end up programmed with IRD = 0 and the app will fail in a mysterious way. Fix this by using "ep->ird" instead of "ep->ord" in the intended place. Signed-off-by: Roland Dreier <rolandd@cisco.com> Acked-by: Steve Wise <swise@opengridcomputing.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2008-03-28 10:45:32 -07:00
..
amso1100	[NET]: Nuke SET_MODULE_OWNER macro.	2007-10-10 16:51:13 -07:00
cxgb3	RDMA/cxgb3: Program hardware IRD with correct value	2008-03-28 10:45:32 -07:00
ehca	IB/ehca: Add PMA support	2008-02-04 20:20:42 -08:00
ipath	IB/ipath: Reset the retry counter for RDMA_READ_RESPONSE_MIDDLE packets	2008-03-11 14:04:35 -07:00
mlx4	IB/mlx4: mlx4_ib_fmr_alloc() should call mlx4_fmr_enable()	2008-02-14 10:39:36 -08:00
mthca	IB/mthca: Free correct MPT on error exit from mthca_fmr_alloc()	2008-02-19 10:42:50 -08:00
nes	RDMA/nes: Fix MSS calculation on RDMA path	2008-03-21 13:59:28 -07:00