diff options
author | 2025-03-13 02:36:40 +0000 | |
---|---|---|
committer | 2025-04-17 11:00:03 +0200 | |
commit | ab244a394c7f13f6573744b9ca72bb22151a3ec4 (patch) | |
tree | c7b327793255c0225d7e86ad272d033a1f0561b6 /net/lapb/lapb_timer.c | |
parent | Merge branch 'xfrm & bonding: Correct use of xso.real_dev' (diff) | |
download | wireguard-linux-ab244a394c7f13f6573744b9ca72bb22151a3ec4.tar.xz wireguard-linux-ab244a394c7f13f6573744b9ca72bb22151a3ec4.zip |
xfrm: Migrate offload configuration
Add hardware offload configuration to XFRM_MSG_MIGRATE
using an option netlink attribute XFRMA_OFFLOAD_DEV.
In the existing xfrm_state_migrate(), the xfrm_init_state()
is called assuming no hardware offload by default. Even the
original xfrm_state is configured with offload, the setting will
be reset. If the device is configured with hardware offload,
it's reasonable to allow the device to maintain its hardware
offload mode. But the device will end up with offload disabled
after receiving a migration event when the device migrates the
connection from one netdev to another one.
The devices that support migration may work with different
underlying networks, such as mobile devices. The hardware setting
should be forwarded to the different netdev based on the
migration configuration. This change provides the capability
for user space to migrate from one netdev to another.
Test: Tested with kernel test in the Android tree located
in https://android.googlesource.com/kernel/tests/
The xfrm_tunnel_test.py under the tests folder in
particular.
Signed-off-by: Chiachang Wang <chiachangwang@google.com>
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
Diffstat (limited to 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions