Searched hist:d4e5db6452211467f668521f5a3bd3c3928918e1 (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/net/tls/ |
| H A D | tls_strp.c | diff d4e5db6452211467f668521f5a3bd3c3928918e1 Fri Jul 22 18:50:30 CDT 2022 Jakub Kicinski <kuba@kernel.org> tls: rx: device: keep the zero copy status with offload
The non-zero-copy path assumes a full skb with decrypted contents.
This means the device offload would have to CoW the data. Try
to keep the zero-copy status instead, copy the data to user space.
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
|
| H A D | tls.h | diff d4e5db6452211467f668521f5a3bd3c3928918e1 Fri Jul 22 18:50:30 CDT 2022 Jakub Kicinski <kuba@kernel.org> tls: rx: device: keep the zero copy status with offload
The non-zero-copy path assumes a full skb with decrypted contents.
This means the device offload would have to CoW the data. Try
to keep the zero-copy status instead, copy the data to user space.
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
|
| H A D | tls_sw.c | diff d4e5db6452211467f668521f5a3bd3c3928918e1 Fri Jul 22 18:50:30 CDT 2022 Jakub Kicinski <kuba@kernel.org> tls: rx: device: keep the zero copy status with offload
The non-zero-copy path assumes a full skb with decrypted contents.
This means the device offload would have to CoW the data. Try
to keep the zero-copy status instead, copy the data to user space.
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
|