diff options
author | Chuck Lever <chuck.lever@oracle.com> | 2017-08-28 15:06:22 -0400 |
---|---|---|
committer | J. Bruce Fields <bfields@redhat.com> | 2017-09-05 15:15:31 -0400 |
commit | 26fb2254dd33b02a522fac42745693f5969b7d4b (patch) | |
tree | d1d9fd4b08b7b87465d9bebebd013b960739318b /fs/nfsd | |
parent | 0062818298662d0d05061949d12880146b5ebd65 (diff) | |
download | linux-26fb2254dd33b02a522fac42745693f5969b7d4b.tar.gz linux-26fb2254dd33b02a522fac42745693f5969b7d4b.tar.xz |
svcrdma: Estimate Send Queue depth properly
The rdma_rw API adjusts max_send_wr upwards during the
rdma_create_qp() call. If the ULP actually wants to take advantage
of these extra resources, it must increase the size of its send
completion queue (created before rdma_create_qp is called) and
increase its send queue accounting limit.
Use the new rdma_rw_mr_factor API to figure out the correct value
to use for the Send Queue and Send Completion Queue depths.
And, ensure that the chosen Send Queue depth for a newly created
transport does not overrun the QP WR limit of the underlying device.
Lastly, there's no longer a need to carry the Send Queue depth in
struct svcxprt_rdma, since the value is used only in the
svc_rdma_accept() path.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'fs/nfsd')
0 files changed, 0 insertions, 0 deletions