summaryrefslogtreecommitdiff
path: root/ipc/mqueue.c
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2017-02-08 21:59:54 (GMT)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-03-12 05:41:52 (GMT)
commitfab6c2caa48f892c4f3446aea9e253ca8a6187a6 (patch)
tree528353702b23688bd7d0f3617708c22bcea31219 /ipc/mqueue.c
parentec3bc2c5ed576c27e4c89a4fc1654755a0fe71bb (diff)
downloadlinux-fab6c2caa48f892c4f3446aea9e253ca8a6187a6.tar.xz
xprtrdma: Per-connection pad optimization
commit b5f0afbea4f2ea52c613ac2b06cb6de2ea18cb6d upstream. Pad optimization is changed by echoing into /proc/sys/sunrpc/rdma_pad_optimize. This is a global setting, affecting all RPC-over-RDMA connections to all servers. The marshaling code picks up that value and uses it for decisions about how to construct each RPC-over-RDMA frame. Having it change suddenly in mid-operation can result in unexpected failures. And some servers a client mounts might need chunk round-up, while others don't. So instead, copy the pad_optimize setting into each connection's rpcrdma_ia when the transport is created, and use the copy, which can't change during the life of the connection, instead. This also removes a hack: rpcrdma_convert_iovs was using the remote-invalidation-expected flag to predict when it could leave out Write chunk padding. This is because the Linux server handles implicit XDR padding on Write chunks correctly, and only Linux servers can set the connection's remote-invalidation-expected flag. It's more sensible to use the pad optimization setting instead. Fixes: 677eb17e94ed ("xprtrdma: Fix XDR tail buffer marshalling") Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'ipc/mqueue.c')
0 files changed, 0 insertions, 0 deletions