svcrdma: Limit ORD based on client's advertised IRD
authorTom Tucker <tom@opengridcomputing.com>
Tue, 20 May 2008 00:00:24 +0000 (19:00 -0500)
committerTom Tucker <tom@opengridcomputing.com>
Wed, 2 Jul 2008 20:01:59 +0000 (15:01 -0500)
commit36ef25e464dbc5820c22a9b2f619b787eda594df
tree4990dfaaf2f4f082ebb016a8a75d3975a6ccf7b8
parent779a48577ba88b6a7e9748a04b0b739f36c5e6f6
svcrdma: Limit ORD based on client's advertised IRD

When adapters have differing IRD limits, the RDMA transport will fail to
connect properly. The RDMA transport should use the client's advertised
inbound read limit when computing its outbound read limit. For iWARP
transports, there is currently no standard for exchanging IRD/ORD
during connection establishment so the 'responder_resources' field in the
connect event is the local device's limit. The RDMA transport can be
configured to use a smaller ORD by writing the desired number to the
/proc/sys/sunrpc/svc_rdma/max_outbound_read_requests file.

Signed-off-by: Tom Tucker <tom@opengridcomputing.com>
net/sunrpc/xprtrdma/svc_rdma_transport.c