Commit 3403051e authored by Steve Wise's avatar Steve Wise Committed by Doug Ledford
Browse files

RDMA/Core: remove rdma_cap_read_multi_sge() helper 



This functionality already exists via the max_sge_rd
device capability.

Signed-off-by: default avatarSteve Wise <swise@opengridcomputing.com>
Signed-off-by: default avatarDoug Ledford <dledford@redhat.com>
parent bc3fe2e3

include/rdma/ib_verbs.h

+0 −28
Original line number Diff line number Diff line
@@ -2070,34 +2070,6 @@ static inline bool rdma_cap_eth_ah(const struct ib_device *device, u8 port_num) 
	return device->port_immutable[port_num].core_cap_flags & RDMA_CORE_CAP_ETH_AH;

}



/**

 * rdma_cap_read_multi_sge - Check if the port of device has the capability

 * RDMA Read Multiple Scatter-Gather Entries.

 * @device: Device to check

 * @port_num: Port number to check

 *

 * iWARP has a restriction that RDMA READ requests may only have a single

 * Scatter/Gather Entry (SGE) in the work request.

 *

 * NOTE: although the linux kernel currently assumes all devices are either

 * single SGE RDMA READ devices or identical SGE maximums for RDMA READs and

 * WRITEs, according to Tom Talpey, this is not accurate.  There are some

 * devices out there that support more than a single SGE on RDMA READ

 * requests, but do not support the same number of SGEs as they do on

 * RDMA WRITE requests.  The linux kernel would need rearchitecting to

 * support these imbalanced READ/WRITE SGEs allowed devices.  So, for now,

 * suffice with either the device supports the same READ/WRITE SGEs, or

 * it only gets one READ sge.

 *

 * Return: true for any device that allows more than one SGE in RDMA READ

 * requests.

 */

static inline bool rdma_cap_read_multi_sge(struct ib_device *device,

					   u8 port_num)

{

	return !(device->port_immutable[port_num].core_cap_flags & RDMA_CORE_CAP_PROT_IWARP);

}



/**

 * rdma_max_mad_size - Return the max MAD size required by this RDMA Port.

 *