* Copyright (c) 2014-2017 Oracle.  All rights reserved.
* Copyright (c) 2003-2007 Network Appliance, Inc. All rights reserved.
* allocated when the forward channel is set up.
* memory, which always starts on a good alignment boundary.
* while building chunk lists.
* ((8 + 2) * read segment size) + 1 XDR words, or 244 bytes.
* And the fixed part of the header is another 24 bytes.
* at least 750 bytes are available for RPC messages.
* These structures are allocated during transport initialization.
* struct rpcrdma_buffer. N is the max number of outstanding RPCs.
* Setting this to zero disables Receive post batching.
* completion can do before returning to the provider.
* Setting this to zero disables Send completion batching.
* on the fly (ie, not pre-registered).
* track of registration metadata while each RPC is pending.
* release these resources when an RPC is complete.
* struct rpcrdma_req -- structure central to the request/reply sequence.
* struct rpcrdma_buffer. N is the max number of outstanding requests.
* It includes pre-registered buffer memory for send AND recv.
* struct rpcrdma_req associated with the request.
* depends on the device's max_sge limit.
* inline requests/replies, and client/server credits.
* exists primarily for modularity.
* for convenience. This structure need not be visible externally.
/* Setting this to 0 ensures interoperability with early servers.
* Setting this to 1 enhances certain unaligned read/write performance.
* Wrappers for chunk registration, shared by read/write chunk code.