From: Stefan Roesch <[email protected]>
To: Jens Axboe <[email protected]>
Cc: [email protected], [email protected],
[email protected],
Olivier Langlois <[email protected]>,
Jakub Kicinski <[email protected]>
Subject: Re: [PATCH v10 2/5] io-uring: add napi busy poll support
Date: Thu, 27 Apr 2023 10:44:49 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Jens Axboe <[email protected]> writes:
> On 4/26/23 7:41?PM, Jens Axboe wrote:
>>> +static void io_napi_multi_busy_loop(struct list_head *napi_list,
>>> + struct io_wait_queue *iowq)
>>> +{
>>> + unsigned long start_time = busy_loop_current_time();
>>> +
>>> + do {
>>> + if (list_is_singular(napi_list))
>>> + break;
>>> + if (!__io_napi_busy_loop(napi_list, iowq->napi_prefer_busy_poll))
>>> + break;
>>> + } while (!io_napi_busy_loop_should_end(iowq, start_time));
>>> +}
>>
>> Do we need to check for an empty list here?
>>
>>> +static void io_napi_blocking_busy_loop(struct list_head *napi_list,
>>> + struct io_wait_queue *iowq)
>>> +{
>>> + if (!list_is_singular(napi_list))
>>> + io_napi_multi_busy_loop(napi_list, iowq);
>>> +
>>> + if (list_is_singular(napi_list)) {
>>> + struct io_napi_ht_entry *ne;
>>> +
>>> + ne = list_first_entry(napi_list, struct io_napi_ht_entry, list);
>>> + napi_busy_loop(ne->napi_id, io_napi_busy_loop_should_end, iowq,
>>> + iowq->napi_prefer_busy_poll, BUSY_POLL_BUDGET);
>>> + }
>>> +}
>>
>> Presumably io_napi_multi_busy_loop() can change the state of the list,
>> which is why we have if (cond) and then if (!cond) here? Would probably
>> warrant a comment as it looks a bit confusing.
>
> Doesn't look like that's the case? We just call into
> io_napi_multi_busy_loop() -> napi_busy_loop() which doesn't touch it. So
> the state should be the same?
>
> We also check if the list isn't singular before we call it, and then
> io_napi_multi_busy_loop() breaks out of the loop if it is. And we know
> it's not singular when calling, and I don't see what changes it.
>
> Unless I'm missing something, which is quite possible, this looks overly
> convoluted and has extra pointless checks?
I'll fix it.
next prev parent reply other threads:[~2023-04-27 17:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 18:18 [PATCH v10 0/5] io_uring: add napi busy polling support Stefan Roesch
2023-04-25 18:18 ` [PATCH v10 1/5] io-uring: move io_wait_queue definition to header file Stefan Roesch
2023-04-25 18:18 ` [PATCH v10 2/5] io-uring: add napi busy poll support Stefan Roesch
2023-04-27 1:41 ` Jens Axboe
2023-04-27 1:46 ` Jens Axboe
2023-04-27 17:34 ` Stefan Roesch
2023-04-27 1:50 ` Jens Axboe
2023-04-27 1:59 ` Jens Axboe
2023-04-27 18:21 ` Stefan Roesch
2023-04-27 17:44 ` Stefan Roesch [this message]
2023-04-27 16:27 ` Stefan Roesch
2023-04-28 1:09 ` Jens Axboe
2023-04-27 2:56 ` Ammar Faizi
2023-04-27 11:16 ` Jens Axboe
2023-04-25 18:18 ` [PATCH v10 3/5] io-uring: add sqpoll support for napi busy poll Stefan Roesch
2023-04-25 18:18 ` [PATCH v10 4/5] io_uring: add register/unregister napi function Stefan Roesch
2023-04-25 18:18 ` [PATCH v10 5/5] io_uring: add prefer busy poll to register and unregister napi api 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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