From: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
To: khorenko@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1 v2 0/1] selftests/bpf: run the xsk veth tests in a network namespace of their own
Date: Thu, 22 Oct 2026 05:47:46 +0300 [thread overview]
Message-ID: <20261022024816.2435565-1-eva.kurchatova@virtuozzo.com> (raw)
Changes in v2:
- -f is checked as the sysctl is, 1 to 45 and digits only, so a value
that would wrap the fragment count or the packet array is refused.
- -f goes into the namespace only when the host's sysctl file could be
read; a bare -f made getopts complain.
- No network namespace skips the tests, as no veth support does, rather
than failing them.
- The -f description says the option tells the tests the kernel's limit
and changes nothing in the kernel.
- The -d hint names the namespace in a usable form.
- test_exit() exits 1 for a skip as it does for the veth one; as the
script has it.
Link to v1: http://lore.virtuozzo.com/kernel/20261020041218.1659392-1-eva.kurchatova@virtuozzo.com/T/#t
Eva Kurchatova (1):
selftests/bpf: run the xsk veth tests in a network namespace of their
own
tools/testing/selftests/bpf/test_xsk.sh | 32 ++++++++++++++++++++++--
tools/testing/selftests/bpf/xskxceiver.c | 17 +++++++++++--
2 files changed, 45 insertions(+), 4 deletions(-)
--
2.56.0
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next reply other threads:[~2026-10-22 2:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 2:47 Eva Kurchatova [this message]
2026-10-22 2:47 ` [Devel] [PATCH hci-8.1 v2 1/1] " Eva Kurchatova
2026-10-22 2:53 ` no-reply
2026-10-22 3:06 ` Eva Kurchatova (Virtuozzo)
2026-10-22 16:14 ` Konstantin Khorenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261022024816.2435565-1-eva.kurchatova@virtuozzo.com \
--to=eva.kurchatova@virtuozzo.com \
--cc=devel@openvz.org \
--cc=khorenko@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.