From: Stefan Roesch <shr@devkernel.io>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: Facebook Kernel Team <kernel-team@fb.com>,
Jens Axboe <axboe@kernel.dk>,
Olivier Langlois <olivier@trillion01.com>,
Jakub Kicinski <kuba@kernel.org>,
netdev Mailing List <netdev@vger.kernel.org>,
io-uring Mailing List <io-uring@vger.kernel.org>
Subject: Re: [RFC PATCH v1 3/3] liburing: add test programs for napi busy poll
Date: Mon, 07 Nov 2022 09:57:04 -0800 [thread overview]
Message-ID: <qvqwr0yeabqa.fsf@dev0134.prn3.facebook.com> (raw)
In-Reply-To: <d9761f0b-0a31-1ec9-66b8-371cb22250f9@gnuweeb.org>
Ammar Faizi <ammarfaizi2@gnuweeb.org> writes:
> On 11/4/22 3:40 AM, Stefan Roesch wrote:
>> +struct option longopts[] =
>> +{
>> + {"address" , 1, NULL, 'a'},
>> + {"busy" , 0, NULL, 'b'},
>> + {"help" , 0, NULL, 'h'},
>> + {"num_pings", 1, NULL, 'n'},
>> + {"port" , 1, NULL, 'p'},
>> + {"sqpoll" , 0, NULL, 's'},
>> + {"timeout" , 1, NULL, 't'},
>
> Inconsistent indentation.
>
Version 2 of the patch fixes this.
>> + if (strlen(opt.addr) == 0) {
>> + fprintf(stderr, "address option is mandatory\n");
>> + printUsage(argv[0]);
>> + exit(-1);
>> + }
> Don't use integer literal like 0 or -1 as the exit code in tests, use the
> exit code protocol:
>
> T_EXIT_PASS
> T_EXIT_FAIL
> T_EXIT_SKIP
>
> They are defined in test/helpers.h.
Version 2 of the patch uses the above constants.
next prev parent reply other threads:[~2022-11-07 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 20:40 [RFC PATCH v1 0/3] liburing: add api for napi busy poll timeout Stefan Roesch
2022-11-03 20:40 ` [RFC PATCH v1 1/3] liburing: add api to set " Stefan Roesch
2022-11-03 21:55 ` Ammar Faizi
2022-11-07 17:54 ` Stefan Roesch
2022-11-03 22:09 ` Ammar Faizi
2022-11-07 17:56 ` Stefan Roesch
2022-11-03 20:40 ` [RFC PATCH v1 2/3] liburing: add documentation for new napi busy polling Stefan Roesch
2022-11-03 20:40 ` [RFC PATCH v1 3/3] liburing: add test programs for napi busy poll Stefan Roesch
2022-11-03 22:04 ` Ammar Faizi
2022-11-07 17:57 ` Stefan Roesch [this message]
2022-11-03 22:20 ` Ammar Faizi
2022-11-07 17:58 ` Stefan Roesch
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=qvqwr0yeabqa.fsf@dev0134.prn3.facebook.com \
--to=shr@devkernel.io \
--cc=ammarfaizi2@gnuweeb.org \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olivier@trillion01.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 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).