Eddie Wai a25d112fe9 RDMA/bnxt_re: Fixed the max_rd_atomic support for initiator and destination QP ... There's a couple of bugs in the support of max_rd_atomic and max_dest_rd_atomic. In the modify_qp, if the requested max_rd_atomic, which is the ORRQ size, is greater than what the chip can support, then we have to cap the request to chip max as we can't have the HW overflow the ORRQ. Capping the max_rd_atomic support internally is okay to do as the remaining read/atomic WRs will still be sitting in the SQ. However, for the max_dest_rd_atomic, the driver has to error out as this dictates the IRRQ size and we can't control what the remote side sends. Signed-off-by: Eddie Wai <eddie.wai@broadcom.com> Signed-off-by: Selvin Xavier <selvin.xavier@broadcom.com> Signed-off-by: Doug Ledford <dledford@redhat.com>		2017-07-20 11:20:50 -04:00
..
core	IB/core: Allow QP state transition from reset to error	2017-07-17 21:21:30 -04:00
hw	RDMA/bnxt_re: Fixed the max_rd_atomic support for initiator and destination QP	2017-07-20 11:20:50 -04:00
sw	IB/rxe: Set dma_mask and coherent_dma_mask	2017-07-17 21:21:27 -04:00
ulp	IB/IPoIB: Fix error code in ipoib_add_port()	2017-07-20 11:20:49 -04:00
Kconfig	IB/opa-vnic: Virtual Network Interface Controller (VNIC) netdev	2017-04-20 12:01:38 -04:00
Makefile	IB/rdmavt: Create module framework and handle driver registration	2016-03-10 20:37:04 -05:00