summaryrefslogtreecommitdiff
path: root/net/sunrpc/Kconfig
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2019-08-20 01:40:11 +0300
committerAnna Schumaker <Anna.Schumaker@Netapp.com>2019-08-20 18:09:46 +0300
commitf3c66a2f56683a20ced4e700a8167d6b357641da (patch)
tree380ffa5675a37fd9fbac23c9d47e9b96f8100edf /net/sunrpc/Kconfig
parent36bdd9056b6a83d573ffdde282a5a91ce734c536 (diff)
downloadlinux-f3c66a2f56683a20ced4e700a8167d6b357641da.tar.xz
xprtrdma: Boost maximum transport header size
Although I haven't seen any performance results that justify it, I've received several complaints that NFS/RDMA no longer supports a maximum rsize and wsize of 1MB. These days it is somewhat smaller. To simplify the logic that determines whether a chunk list is necessary, the implementation uses a fixed maximum size of the transport header. Currently that maximum size is 256 bytes, one quarter of the default inline threshold size for RPC/RDMA v1. Since commit a78868497c2e ("xprtrdma: Reduce max_frwr_depth"), the size of chunks is also smaller to take advantage of inline page lists in device internal MR data structures. The combination of these two design choices has reduced the maximum NFS rsize and wsize that can be used for most RNIC/HCAs. Increasing the maximum transport header size and the maximum number of RDMA segments it can contain increases the negotiated maximum rsize/wsize on common RNIC/HCAs. Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'net/sunrpc/Kconfig')
0 files changed, 0 insertions, 0 deletions