diff options
| author | Willem de Bruijn <[email protected]> | 2025-06-30 19:42:12 +0000 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2025-07-02 22:07:16 +0000 |
| commit | 81d572a551f43c01380e4aa39a6b9f331c931fbc (patch) | |
| tree | 5170087b9fb795ee9716a70f5f93543f03ad7894 /drivers/vhost/net.c | |
| parent | net: preserve MSG_ZEROCOPY with forwarding (diff) | |
| download | kernel-81d572a551f43c01380e4aa39a6b9f331c931fbc.tar.gz kernel-81d572a551f43c01380e4aa39a6b9f331c931fbc.zip | |
selftest: net: extend msg_zerocopy test with forwarding
Zerocopy skbs are converted to regular copy skbs when data is queued
to a local socket. This happens in the existing test with a sender and
receiver communicating over a veth device.
Zerocopy skbs are sent without copying if egressing a device. Verify
that this behavior is maintained even in the common container setup
where data is forwarded over a veth to the physical device.
Update msg_zerocopy.sh to
1. Have a dummy network device to simulate a physical device.
2. Have forwarding enabled between veth and dummy.
3. Add a tx-only test that sends out dummy via the forwarding path.
4. Verify the exitcode of the sender, which signals zerocopy success.
As dummy drops all packets, this cannot be a TCP connection. Test
the new case with unconnected UDP only.
Update msg_zerocopy.c to
- Accept an argument whether send with zerocopy is expected.
- Return an exitcode whether behavior matched that expectation.
Signed-off-by: Willem de Bruijn <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'drivers/vhost/net.c')
0 files changed, 0 insertions, 0 deletions
