xprtrdma: Manage MRs in context of a single connection

Browse source

MRs are now allocated on demand so we can safely throw them away on
disconnect. This way an idle transport can disconnect and it won't
pin hardware MR resources.

Two additional changes:

- Now that all MRs are destroyed on disconnect, there's no need to
  check during header marshaling if a req has MRs to recycle. Each
  req is sent only once per connection, and now rl_registered is
  guaranteed to be empty when rpcrdma_marshal_req is invoked.

- Because MRs are now destroyed in a WQ_MEM_RECLAIM context, they
  also must be allocated in a WQ_MEM_RECLAIM context. This reduces
  the likelihood that device driver memory allocation will trigger
  memory reclaim during NFS writeback.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

...

This commit is contained in:

Chuck Lever 2019-10-09 13:07:48 -04:00 • committed by Anna Schumaker

parent c3700780a0

commit 9d2da4ff00

4 changed files with 40 additions and 57 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

24

net/sunrpc/xprtrdma/frwr_ops.c

View file

9

net/sunrpc/xprtrdma/rpc_rdma.c

View file

62

net/sunrpc/xprtrdma/verbs.c

View file

2

net/sunrpc/xprtrdma/xprt_rdma.h

View file