From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: "Alexis Lothoré (eBPF Foundation)" <alexis.lothore@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>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jesper Dangaard Brouer <hawk@kernel.org>,
Lorenzo Bianconi <lorenzo@kernel.org>,
ebpf@linuxfoundation.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: convert test_xdp_features.sh to test_progs
Date: Mon, 9 Sep 2024 23:18:00 +0200 [thread overview]
Message-ID: <20240909231800.72b6b328@fedora.home> (raw)
In-Reply-To: <20240909-convert_xdp_tests-v1-1-925be5fbee3c@bootlin.com>
Hi Alexis,
On Mon, 09 Sep 2024 22:02:07 +0200
Alexis Lothoré (eBPF Foundation) <alexis.lothore@bootlin.com> wrote:
> test_xdp_features.sh is a shell script allowing to test that xdp features
> advertised by an interface are indeed delivered. The test works by starting
> two instance of the same program, both attaching specific xdp programs to
> each side of a veth link, and then make those programs manage packets and
> collect stats to check whether tested XDP feature is indeed delivered or
> not. However this test is not integrated in test_progs framework and so can
> not run automatically in CI.
>
> Rewrite test_xdp_features to integrate it in test_progs so it can run
> automatically in CI. The main changes brought by the rewrite are the
> following:
> - instead of running to separated processes (each one managing either the
> tester veth or the DUT vet), run a single process
> - slightly change testing direction (v0 is the tester in local namespace,
> v1 is the Device Under Test in remote namespace)
> - group all tests previously managed by test_xdp_features as subtests (one
> per tested XDP feature). As a consequence, run only once some steps
> instead of once per subtest (eg: starting/stopping the udp server). On
> the contrary, make sure that each subtest properly cleans up its state
> (ie detach xdp programs, reset test stats, etc)
> - since there is now a single process, get rid of the "control" tcp channel
> used to configure DUT. Configuring the DUT now only consists in switching
> to DUT network namespace and run the relevant commands
> - since there is no more control channel, get rid of TLVs, keep only the
> CMD_ECHO packet type, and set it as a magic
> - simplify network setup: use only ipv6 instead of both ipv4 and ipv6,
> force static neighbours instead of waiting for autoconfiguration, do not
> force gro (fetch xdp features only once xdp programs are loaded instead)
>
> The existing XDP programs are reused, with some minor changes:
> - tester and dut stats maps are converted to global variables for easier
> usage
> - programs do not use TLV struct anymore but the magic replacing the echo
> command
> - avoid to accidentally make tests pass: drop packets instead of forwarding
> them to userspace when they do not match the expected payload
>
> Signed-off-by: Alexis Lothoré (eBPF Foundation) <alexis.lothore@bootlin.com>
I'm far for having reviewed the whole patch, but I do have one comment
below :)
[...]
> +static void *run_dut_echo_thread(void *arg)
> +{
> + struct test_data *t = (struct test_data *)arg;
> + __u32 magic;
> +
> + while (!t->quit_dut_echo_thread) {
> + struct sockaddr_storage addr;
> + socklen_t addrlen;
> + size_t n;
> +
> + n = recvfrom(t->echo_server_sock, &magic, sizeof(magic),
> + MSG_WAITALL, (struct sockaddr *)&addr, &addrlen);
> + if (n != sizeof(magic)) {
> + usleep(LOOP_DELAY_US);
> + continue;
> + }
> +
> + if (htonl(magic) != CMD_ECHO)
> + continue;
Shouldn't it be ntohl here ? The former code used the ntohs helper for
that command, and you're sending the magic in send_echo_msg with a
htonl() so I guess here you might want to convert the value back to
host endianness.
Thanks,
Maxime
next prev parent reply other threads:[~2024-09-09 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 20:02 [PATCH bpf-next] selftests/bpf: convert test_xdp_features.sh to test_progs Alexis Lothoré (eBPF Foundation)
2024-09-09 21:18 ` Maxime Chevallier [this message]
2024-09-10 7:15 ` Alexis Lothoré
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=20240909231800.72b6b328@fedora.home \
--to=maxime.chevallier@bootlin.com \
--cc=alexis.lothore@bootlin.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=ebpf@linuxfoundation.org \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--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