diff options
author | Chuck Lever <[email protected]> | 2016-06-29 13:55:06 -0400 |
---|---|---|
committer | Anna Schumaker <[email protected]> | 2016-07-11 15:50:43 -0400 |
commit | 65b80179f9b8171b74625febf3457f41e792fa23 (patch) | |
tree | 91ed3dcb91c5bab4967ddfdf85132bb7b579a700 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 64695bde6c289a62250eb0a078916703c8cf639a (diff) |
xprtrdma: No direct data placement with krb5i and krb5p
Direct data placement is not allowed when using flavors that
guarantee integrity or privacy. When such security flavors are in
effect, don't allow the use of Read and Write chunks for moving
individual data items. All messages larger than the inline threshold
are sent via Long Call or Long Reply.
On my systems (CX-3 Pro on FDR), for small I/O operations, the use
of Long messages adds only around 5 usecs of latency in each
direction.
Note that when integrity or encryption is used, the host CPU touches
every byte in these messages. Even if it could be used, data
movement offload doesn't buy much in this case.
Signed-off-by: Chuck Lever <[email protected]>
Tested-by: Steve Wise <[email protected]>
Signed-off-by: Anna Schumaker <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions