diff options
author | Chuck Lever <chuck.lever@oracle.com> | 2016-09-15 16:55:37 +0200 |
---|---|---|
committer | Anna Schumaker <Anna.Schumaker@Netapp.com> | 2016-09-19 19:08:37 +0200 |
commit | 68778945e46f143ed7974b427a8065f69a4ce944 (patch) | |
tree | a513ebe3eb2dd881a67bd55a3a0aa3d525eb4463 /net/phonet | |
parent | SUNRPC: Generalize the RPC buffer release API (diff) | |
download | linux-68778945e46f143ed7974b427a8065f69a4ce944.tar.xz linux-68778945e46f143ed7974b427a8065f69a4ce944.zip |
SUNRPC: Separate buffer pointers for RPC Call and Reply messages
For xprtrdma, the RPC Call and Reply buffers are involved in real
I/O operations.
To start with, the DMA direction of the I/O for a Call is opposite
that of a Reply.
In the current arrangement, the Reply buffer address is on a
four-byte alignment just past the call buffer. Would be friendlier
on some platforms if that was at a DMA cache alignment instead.
Because the current arrangement allocates a single memory region
which contains both buffers, the RPC Reply buffer often contains a
page boundary in it when the Call buffer is large enough (which is
frequent).
It would be a little nicer for setting up DMA operations (and
possible registration of the Reply buffer) if the two buffers were
separated, well-aligned, and contained as few page boundaries as
possible.
Now, I could just pad out the single memory region used for the pair
of buffers. But frequently that would mean a lot of unused space to
ensure the Reply buffer did not have a page boundary.
Add a separate pointer to rpc_rqst that points right to the RPC
Reply buffer. This makes no difference to xprtsock, but it will help
xprtrdma in subsequent patches.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'net/phonet')
0 files changed, 0 insertions, 0 deletions