lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 26 Jan 2017 07:50:54 +0100 From: Steffen Klassert <steffen.klassert@...unet.com> To: <netdev@...r.kernel.org> CC: Steffen Klassert <steffen.klassert@...unet.com>, David Miller <davem@...emloft.net>, Eric Dumazet <eric.dumazet@...il.com>, "Sowmini Varadhan" <sowmini.varadhan@...cle.com>, Ilan Tayari <ilant@...lanox.com> Subject: [PATCH RFC ipsec-next] IPsec GRO This introduces a device independent napi instance that handles GRO for IPsec. I was not able to use gro cells directly because I don't have a netdevice where I can hang off the napi instance. We now may have a secpath at a GRO merged skb, so we need to drop it. This is the only cange to the generic networking code. The packet still travels two times through the stack, but might be aggregated in the second round. We can avoid the second round with implementing GRO callbacks for the IPsec protocols. This will be a separate patchset as this needs some more generic networking changes because of the asynchronous nature of IPsec.
Powered by blists - more mailing lists