diff options
author | 2016-01-07 14:49:12 -0500 | |
---|---|---|
committer | 2016-01-19 15:30:48 -0500 | |
commit | cc886c9ff1607eda04062bdcec963e2f8e6a3eb1 (patch) | |
tree | 26cb6dea78b0a3fbdcab65159a180de1fbba7aec /tools/perf/scripts/python/export-to-postgresql.py | |
parent | svcrdma: Clean up process_context() (diff) | |
download | wireguard-linux-cc886c9ff1607eda04062bdcec963e2f8e6a3eb1.tar.xz wireguard-linux-cc886c9ff1607eda04062bdcec963e2f8e6a3eb1.zip |
svcrdma: Improve allocation of struct svc_rdma_op_ctxt
When the maximum payload size of NFS READ and WRITE was increased
by commit cc9a903d915c ("svcrdma: Change maximum server payload back
to RPCSVC_MAXPAYLOAD"), the size of struct svc_rdma_op_ctxt
increased to over 6KB (on x86_64). That makes allocating one of
these from a kmem_cache more likely to fail in situations when
system memory is exhausted.
Since I'm about to add a caller where this allocation must always
work _and_ it cannot sleep, pre-allocate ctxts for each connection.
Another motivation for this change is that NFSv4.x servers are
required by specification not to drop NFS requests. Pre-allocating
memory resources reduces the likelihood of a drop.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Acked-by: Bruce Fields <bfields@fieldses.org>
Signed-off-by: Doug Ledford <dledford@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions