diff options
| author | Tom Tucker <tom@opengridcomputing.com> | 2008-05-19 19:00:24 -0500 |
|---|---|---|
| committer | Tom Tucker <tom@opengridcomputing.com> | 2008-07-02 15:01:59 -0500 |
| commit | 36ef25e464dbc5820c22a9b2f619b787eda594df (patch) | |
| tree | 4990dfaaf2f4f082ebb016a8a75d3975a6ccf7b8 /net/netlink/af_netlink.c | |
| parent | 779a48577ba88b6a7e9748a04b0b739f36c5e6f6 (diff) | |
| download | blackbird-op-linux-36ef25e464dbc5820c22a9b2f619b787eda594df.tar.gz blackbird-op-linux-36ef25e464dbc5820c22a9b2f619b787eda594df.zip | |
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>
Diffstat (limited to 'net/netlink/af_netlink.c')
0 files changed, 0 insertions, 0 deletions
