diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2015-08-03 13:03:49 -0400 |
|---|---|---|
| committer | Anna Schumaker <Anna.Schumaker@Netapp.com> | 2015-08-05 16:21:27 -0400 |
| commit | 5457ced0b504b41afe9439a6533066dea2fc0e1a (patch) | |
| tree | a609ee8cf9c21fe64975759d80471aa88d159ddd /Documentation/filesystems/ncpfs.txt | |
| parent | b3221d6a53c44cd572a3a400abdd1e2a24bea587 (diff) | |
| download | linux-5457ced0b504b41afe9439a6533066dea2fc0e1a.tar.gz linux-5457ced0b504b41afe9439a6533066dea2fc0e1a.tar.bz2 linux-5457ced0b504b41afe9439a6533066dea2fc0e1a.zip | |
xprtrdma: Account for RPC/RDMA header size when deciding to inline
When the size of the RPC message is near the inline threshold (1KB),
the client would allow messages to be sent that were a few bytes too
large.
When marshaling RPC/RDMA requests, ensure the combined size of
RPC/RDMA header and RPC header do not exceed the inline threshold.
Endpoints typically reject RPC/RDMA messages that exceed the size
of their receive buffers.
The two server implementations I test with (Linux and Solaris) use
receive buffers that are larger than the client’s inline threshold.
Thus so far this has been benign, observed only by code inspection.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Reviewed-by: Devesh Sharma <devesh.sharma@avagotech.com>
Tested-by: Devesh Sharma <devesh.sharma@avagotech.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'Documentation/filesystems/ncpfs.txt')
0 files changed, 0 insertions, 0 deletions