svcrdma: Optimize the logic that selects the R_key to invalidate

Browse source

o Select the R_key to invalidate while the CPU cache still contains
  the received RPC Call transport header, rather than waiting until
  we're about to send the RPC Reply.

o Choose Send With Invalidate if there is exactly one distinct R_key
  in the received transport header. If there's more than one, the
  client will have to perform local invalidation after it has
  already waited for remote invalidation.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>

...

This commit is contained in:

Chuck Lever 2018-11-27 11:11:35 -05:00 • committed by J. Bruce Fields

parent b493fd31c0

commit 97bce63408

3 changed files with 77 additions and 40 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

1

include/linux/sunrpc/svc_rdma.h

View file

63

net/sunrpc/xprtrdma/svc_rdma_recvfrom.c

View file

53

net/sunrpc/xprtrdma/svc_rdma_sendto.c

View file