aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorChuck Lever <[email protected]>2015-03-30 14:34:02 -0400
committerAnna Schumaker <[email protected]>2015-03-31 09:52:52 -0400
commit805272406a980cab0e11742e5423ba97b6f38836 (patch)
tree89f49bc3a2d999fe4c67339fef0cb767eccaf7b1 /tools/perf/scripts/python/call-graph-from-postgresql.py
parente23779451ee05e824fedbb68bd17fc5c77e40166 (diff)
xprtrdma: Byte-align FRWR registration
The RPC/RDMA transport's FRWR registration logic registers whole pages. This means areas in the first and last pages that are not involved in the RDMA I/O are needlessly exposed to the server. Buffered I/O is typically page-aligned, so not a problem there. But for direct I/O, which can be byte-aligned, and for reply chunks, which are nearly always smaller than a page, the transport could expose memory outside the I/O buffer. FRWR allows byte-aligned memory registration, so let's use it as it was intended. Reported-by: Sagi Grimberg <[email protected]> Signed-off-by: Chuck Lever <[email protected]> Tested-by: Devesh Sharma <[email protected]> Tested-by: Meghana Cheripady <[email protected]> Tested-by: Veeresh U. Kokatnur <[email protected]> Signed-off-by: Anna Schumaker <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions