From: Stanislav Fomichev <stfomichev@gmail.com>
To: "Bastien Curutchet (eBPF Foundation)" <bastien.curutchet@bootlin.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Mykola Lysenko <mykolal@fb.com>,
Shuah Khan <shuah@kernel.org>,
Alexis Lothore <alexis.lothore@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/4] selftests/bpf: tc_links/tc_opts: Unserialize tests
Date: Wed, 19 Feb 2025 08:05:23 -0800 [thread overview]
Message-ID: <Z7YBQ0M_6kzC1ieD@mini-arch> (raw)
In-Reply-To: <20250219-b4-tc_links-v2-0-14504db136b7@bootlin.com>
On 02/19, Bastien Curutchet (eBPF Foundation) wrote:
> Hi all,
>
> Both tc_links.c and tc_opts.c do their tests on the loopback interface.
> It prevents from parallelizing their executions.
>
> Add a new behaviour to the test_progs framework that creates and opens a
> new network namespace to run a test in it. This is done automatically on
> tests whose names start with 'ns_'.
>
> One test already has a name starting with 'ns_', so PATCH 1 renames it
> to avoid conflicts. PATCH 2 introduces the test_progs 'feature'.
> PATCH 3 & 4 convert some tests to use these dedicated namespaces.
>
> Signed-off-by: Bastien Curutchet (eBPF Foundation) <bastien.curutchet@bootlin.com>
> ---
> Changes in v2:
> - Handle the netns creation / opening directly in test_progs
> - Link to v1: https://lore.kernel.org/bpf/e3838d93-04e3-4e96-af53-e9e63550d7ba@bootlin.com
Acked-by: Stanislav Fomichev <sdf@fomichev.me>
Thanks, looks very nice!
next prev parent reply other threads:[~2025-02-19 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 14:52 [PATCH bpf-next v2 0/4] selftests/bpf: tc_links/tc_opts: Unserialize tests Bastien Curutchet (eBPF Foundation)
2025-02-19 14:53 ` [PATCH bpf-next v2 1/4] selftests/bpf: ns_current_pid_tgid: Rename the test function Bastien Curutchet (eBPF Foundation)
2025-02-19 14:53 ` [PATCH bpf-next v2 2/4] selftests/bpf: Optionally open a dedicated namespace to run test in it Bastien Curutchet (eBPF Foundation)
2025-02-19 14:53 ` [PATCH bpf-next v2 3/4] selftests/bpf: tc_links/tc_opts: Unserialize tests Bastien Curutchet (eBPF Foundation)
2025-02-19 14:53 ` [PATCH bpf-next v2 4/4] selftests/bpf: ns_current_pid_tgid: Use test_progs's ns_ feature Bastien Curutchet (eBPF Foundation)
2025-02-19 16:05 ` Stanislav Fomichev [this message]
2025-02-19 18:00 ` [PATCH bpf-next v2 0/4] selftests/bpf: tc_links/tc_opts: Unserialize tests patchwork-bot+netdevbpf
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=Z7YBQ0M_6kzC1ieD@mini-arch \
--to=stfomichev@gmail.com \
--cc=alexis.lothore@bootlin.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bastien.curutchet@bootlin.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yonghong.song@linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox