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
..
core	RDMA/iwcm: Don't access a cm_id after dropping reference	2008-03-10 21:22:22 -07:00
hw	RDMA/cxgb3: Program hardware IRD with correct value	2008-03-28 10:45:32 -07:00
ulp	IPoIB: Allocate priv->tx_ring with vmalloc()	2008-03-12 07:51:03 -07:00
Kconfig	RDMA/nes: Add a driver for NetEffect RNICs	2008-02-04 20:20:45 -08:00
Makefile	RDMA/nes: Add a driver for NetEffect RNICs	2008-02-04 20:20:45 -08:00