summaryrefslogtreecommitdiffstats
path: root/drivers/net/dsa/qca8k.h
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2020-06-22 15:38:57 -0700
committerDavid S. Miller <davem@davemloft.net>2020-06-22 15:38:57 -0700
commit2b3445e8145700b53530228f332ee40e6d9c916b (patch)
tree30e507d7dbcacc0563cd728ac3844e09fda3faf7 /drivers/net/dsa/qca8k.h
parent389cc2f326fd095edc1c09d7713ac9f9dd591f8a (diff)
parent18cb261afd7bf50134e5ccacc5ec91ea16efadd4 (diff)
Merge branch 'bonding-initial-support-for-hardware-crypto-offload'
Jarod Wilson says: ==================== bonding: initial support for hardware crypto offload This is an initial functional implementation for doing pass-through of hardware encryption from bonding device to capable slaves, in active-backup bond setups. This was developed and tested using ixgbe-driven Intel x520 interfaces with libreswan and a transport mode connection, primarily using netperf, with assorted connection failures forced during transmission. The failover works quite well in my testing, and overall performance is right on par with offload when running on a bare interface, no bond involved. Caveats: this is ONLY enabled for active-backup, because I'm not sure how one would manage multiple offload handles for different devices all running at the same time in the same xfrm, and it relies on some minor changes to both the xfrm code and slave device driver code to get things to behave, and I don't have immediate access to any other hardware that could function similarly, but the NIC driver changes are minimal and straight-forward enough that I've included what I think ought to be enough for mlx5 devices too. v2: reordered patches, switched (back) to using CONFIG_XFRM_OFFLOAD to wrap the code additions and wrapped overlooked additions. v3: rebase w/net-next open, add proper cc list to cover letter ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/dsa/qca8k.h')
0 files changed, 0 insertions, 0 deletions