From: Stanislav Fomichev <stfomichev@gmail.com>
To: Mina Almasry <almasrymina@google.com>
Cc: Stanislav Fomichev <sdf@fomichev.me>,
netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next 01/13] selftests: ncdevmem: Add a flag for the selftest
Date: Thu, 12 Sep 2024 14:59:27 -0700 [thread overview]
Message-ID: <ZuNkPyglAJTcJGmC@mini-arch> (raw)
In-Reply-To: <CAHS8izNzP_-CS2FyuUo6xRzumMAFRbkE00DOzmHpjBSkMUP3PA@mail.gmail.com>
On 09/12, Mina Almasry wrote:
> On Thu, Sep 12, 2024 at 10:12 AM Stanislav Fomichev <sdf@fomichev.me> wrote:
> >
> > And rename it to 'probing'. This is gonna be used in the selftests
> > to probe devmem functionality.
> >
> > Cc: Mina Almasry <almasrymina@google.com>
> > Signed-off-by: Stanislav Fomichev <sdf@fomichev.me>
> > ---
> > tools/testing/selftests/net/ncdevmem.c | 11 +++++++++--
> > 1 file changed, 9 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/testing/selftests/net/ncdevmem.c b/tools/testing/selftests/net/ncdevmem.c
> > index 64d6805381c5..352dba211fb0 100644
> > --- a/tools/testing/selftests/net/ncdevmem.c
> > +++ b/tools/testing/selftests/net/ncdevmem.c
> > @@ -523,8 +523,9 @@ void run_devmem_tests(void)
> > int main(int argc, char *argv[])
> > {
> > int is_server = 0, opt;
> > + int probe = 0;
> >
> > - while ((opt = getopt(argc, argv, "ls:c:p:v:q:t:f:")) != -1) {
> > + while ((opt = getopt(argc, argv, "ls:c:p:v:q:t:f:P")) != -1) {
> > switch (opt) {
> > case 'l':
> > is_server = 1;
> > @@ -550,6 +551,9 @@ int main(int argc, char *argv[])
> > case 'f':
> > ifname = optarg;
> > break;
> > + case 'P':
> > + probe = 1;
> > + break;
> > case '?':
> > printf("unknown option: %c\n", optopt);
> > break;
> > @@ -561,7 +565,10 @@ int main(int argc, char *argv[])
> > for (; optind < argc; optind++)
> > printf("extra arguments: %s\n", argv[optind]);
> >
> > - run_devmem_tests();
> > + if (probe) {
> > + run_devmem_tests();
> > + return 0;
> > + }
> >
>
> Before this change:
> ./ncdevmem (runs run_devmem_tests() and exits)
> ./ncdevmem -l: runs devmem tests and listens
>
> And I plan to add, for the tx path:
>
> ./ncdevmem -c: runs devmem tests and does a devmem client.
>
> After this change, running ncdevmem with no flags just exits without
> doing anything; a bit weird IMO, but I'm not opposed if you see an
> upside.
>
> Is your intention with this change to not run the devmem tests on
> listen? Maybe something like:
>
> if (is_server)
> return do_server();
> else if (is_client) /* to be added */
> return do_client();
> else
> run_devmem_tests();
>
> return 0;
>
> ?
SG! That's even better without the extra flag.
next prev parent reply other threads:[~2024-09-12 21:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 17:12 [PATCH net-next 00/13] selftests: ncdevmem: Add ncdevmem to ksft Stanislav Fomichev
2024-09-12 17:12 ` [PATCH net-next 01/13] selftests: ncdevmem: Add a flag for the selftest Stanislav Fomichev
2024-09-12 20:36 ` Mina Almasry
2024-09-12 21:59 ` Stanislav Fomichev [this message]
2024-09-12 17:12 ` [PATCH net-next 02/13] selftests: ncdevmem: Remove validation Stanislav Fomichev
2024-09-12 20:36 ` Mina Almasry
2024-09-12 21:57 ` Stanislav Fomichev
2024-09-13 15:30 ` Mina Almasry
2024-09-13 17:15 ` Stanislav Fomichev
2024-09-13 23:42 ` Mina Almasry
2024-09-12 17:12 ` [PATCH net-next 03/13] selftests: ncdevmem: Redirect all non-payload output to stderr Stanislav Fomichev
2024-09-12 17:12 ` [PATCH net-next 04/13] selftests: ncdevmem: Separate out dmabuf provider Stanislav Fomichev
2024-09-12 20:36 ` Mina Almasry
2024-09-12 17:12 ` [PATCH net-next 05/13] selftests: ncdevmem: Unify error handling Stanislav Fomichev
2024-09-12 20:35 ` Mina Almasry
2024-09-12 21:49 ` Stanislav Fomichev
2024-09-12 17:12 ` [PATCH net-next 06/13] selftests: ncdevmem: Remove client_ip Stanislav Fomichev
2024-09-12 20:35 ` Mina Almasry
2024-09-12 21:48 ` Stanislav Fomichev
2024-09-12 17:12 ` [PATCH net-next 07/13] selftests: ncdevmem: Remove default arguments Stanislav Fomichev
2024-09-12 17:12 ` [PATCH net-next 08/13] selftests: ncdevmem: Switch to AF_INET6 Stanislav Fomichev
2024-09-12 17:12 ` [PATCH net-next 09/13] selftests: ncdevmem: Properly reset flow steering Stanislav Fomichev
2024-09-12 17:12 ` [PATCH net-next 10/13] selftests: ncdevmem: Use YNL to enable TCP header split Stanislav Fomichev
2024-09-14 13:14 ` kernel test robot
2024-09-12 17:12 ` [PATCH net-next 11/13] selftests: ncdevmem: Remove hard-coded queue numbers Stanislav Fomichev
2024-09-12 20:34 ` Mina Almasry
2024-09-12 21:47 ` Stanislav Fomichev
2024-09-26 16:26 ` Mina Almasry
2024-09-27 1:20 ` Stanislav Fomichev
2024-09-12 17:12 ` [PATCH net-next 12/13] selftests: ncdevmem: Move ncdevmem under drivers/net Stanislav Fomichev
2024-09-13 15:38 ` Mina Almasry
2024-09-13 17:19 ` Stanislav Fomichev
2024-09-12 17:12 ` [PATCH net-next 13/13] selftests: ncdevmem: Add automated test Stanislav Fomichev
2024-09-12 20:34 ` Mina Almasry
2024-09-12 19:48 ` [PATCH net-next 00/13] selftests: ncdevmem: Add ncdevmem to ksft Stanislav Fomichev
2024-09-12 21:07 ` Mina Almasry
2024-09-12 21:43 ` Stanislav Fomichev
2024-12-13 1:18 ` Stanislav Fomichev
2024-12-13 17:47 ` Mina Almasry
2024-12-13 18:53 ` Stanislav Fomichev
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=ZuNkPyglAJTcJGmC@mini-arch \
--to=stfomichev@gmail.com \
--cc=almasrymina@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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;
as well as URLs for NNTP newsgroup(s).