[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y91GLP4LCqsGE8kX@localhost.localdomain>
Date: Fri, 3 Feb 2023 18:36:44 +0100
From: Lorenzo Bianconi <lorenzo@...nel.org>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: bpf <bpf@...r.kernel.org>,
Network Development <netdev@...r.kernel.org>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Eric Dumazet <edumazet@...gle.com>,
Jesper Dangaard Brouer <hawk@...nel.org>,
Toke Høiland-Jørgensen <toke@...hat.com>,
Kumar Kartikeya Dwivedi <memxor@...il.com>,
Marek Majtyka <alardam@...il.com>,
Saeed Mahameed <saeedm@...dia.com>, anthony.l.nguyen@...el.com,
Andy Gospodarek <gospo@...adcom.com>, vladimir.oltean@....com,
Felix Fietkau <nbd@....name>, john@...ozen.org,
Leon Romanovsky <leon@...nel.org>,
Simon Horman <simon.horman@...igine.com>,
Ariel Elior <aelior@...vell.com>,
christophe.jaillet@...adoo.fr, ecree.xilinx@...il.com,
"Michael S. Tsirkin" <mst@...hat.com>,
Björn Töpel <bjorn@...nel.org>,
"Karlsson, Magnus" <magnus.karlsson@...el.com>,
"Fijalkowski, Maciej" <maciej.fijalkowski@...el.com>,
intel-wired-lan <intel-wired-lan@...ts.osuosl.org>,
Lorenzo Bianconi <lorenzo.bianconi@...hat.com>,
Martin KaFai Lau <martin.lau@...ux.dev>,
Stanislav Fomichev <sdf@...gle.com>,
gerhard@...leder-embedded.com
Subject: Re: [PATCH v5 bpf-next 8/8] selftests/bpf: introduce XDP compliance
test tool
> On Wed, Feb 1, 2023 at 2:25 AM Lorenzo Bianconi <lorenzo@...nel.org> wrote:
> >
> > Introduce xdp_features tool in order to test XDP features supported by
> > the NIC and match them against advertised ones.
> > In order to test supported/advertised XDP features, xdp_features must
> > run on the Device Under Test (DUT) and on a Tester device.
> > xdp_features opens a control TCP channel between DUT and Tester devices
> > to send control commands from Tester to the DUT and a UDP data channel
> > where the Tester sends UDP 'echo' packets and the DUT is expected to
> > reply back with the same packet. DUT installs multiple XDP programs on the
> > NIC to test XDP capabilities and reports back to the Tester some XDP stats.
>
>
> 'DUT installs...'? what? The device installs XDP programs ?
Hi Alexei,
DUT stands for Device Under Test, I was thinking it is quite a common term.
Sorry for that.
>
> > +
> > + ctrl_sockfd = accept(*sockfd, (struct sockaddr *)&ctrl_addr, &addrlen);
> > + if (ctrl_sockfd < 0) {
> > + fprintf(stderr, "Failed to accept connection on DUT socket\n");
>
> Applied, but overuse of the word 'DUT' is incorrect and confusing.
>
> 'DUT socket' ? what is that?
> 'Invalid DUT address' ? what address?
> The UX in general is not user friendly.
>
> ./xdp_features
> Invalid ifindex
>
> This is not a helpful message.
>
> ./xdp_features eth0
> Starting DUT on device 3
> Failed to accept connection on DUT socket
>
> 'Starting DUT' ? What did it start?
I will post a follow-up patch to clarify them.
Regards,
Lorenzo
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists