aboutsummaryrefslogtreecommitdiff
path: root/net/ceph/messenger.c
diff options
context:
space:
mode:
authorGravatar Ilya Dryomov <idryomov@gmail.com> 2022-01-23 17:27:47 +0100
committerGravatar Ilya Dryomov <idryomov@gmail.com> 2022-02-02 18:50:36 +0100
commit2ea88716369ac9a7486a8cb309d6bf1239ea156c (patch)
tree6aa47e4bd917650d9c888a8dc77494d1bf45d5a1 /net/ceph/messenger.c
parentLinux 5.17-rc2 (diff)
downloadlinux-2ea88716369ac9a7486a8cb309d6bf1239ea156c.tar.gz
linux-2ea88716369ac9a7486a8cb309d6bf1239ea156c.tar.bz2
linux-2ea88716369ac9a7486a8cb309d6bf1239ea156c.zip
libceph: make recv path in secure mode work the same as send path
The recv path of secure mode is intertwined with that of crc mode. While it's slightly more efficient that way (the ciphertext is read into the destination buffer and decrypted in place, thus avoiding two potentially heavy memory allocations for the bounce buffer and the corresponding sg array), it isn't really amenable to changes. Sacrifice that edge and align with the send path which always uses a full-sized bounce buffer (currently there is no other way -- if the kernel crypto API ever grows support for streaming (piecewise) en/decryption for GCM [1], we would be able to easily take advantage of that on both sides). [1] https://lore.kernel.org/all/20141225202830.GA18794@gondor.apana.org.au/ Signed-off-by: Ilya Dryomov <idryomov@gmail.com> Reviewed-by: Jeff Layton <jlayton@kernel.org>
Diffstat (limited to 'net/ceph/messenger.c')
0 files changed, 0 insertions, 0 deletions