From: Olivier Langlois <[email protected]>
To: Pavel Begunkov <[email protected]>,
Jens Axboe <[email protected]>,
[email protected]
Subject: Re: [PATCH 2/2] io_uring: do the sqpoll napi busy poll outside the submission block
Date: Fri, 02 Aug 2024 10:22:14 -0400 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Fri, 2024-08-02 at 12:14 +0100, Pavel Begunkov wrote:
>
> io_do_sqpoll_napi() returns 1 as long as there are napis in the list,
> iow even if there is no activity it'll spin almost forever (60s is
> forever) bypassing sq_thread_idle.
>
> Let's not update sqt_spin here, if the user wants it to poll for
> longer it can pass a larger SQPOLL idle timeout value.
>
>
>
fair enough...
in that case, maybe the man page SQPOLL idle timeout description should
include the mention that if NAPI busy loop is used, the idle timeout
should be at least as large as gro_flush_timeout to meet NAPI
requirement to not generate interrupts as described in
Documentation/networking/napi.rst
section "Software IRQ coalescing"
I have discovered this fact the hard way by having spent days to figure
out how to do busy poll the right way.
this simple mention could save the trouble to many new users of the
feature.
I'll rework the patch and send a new version in the few days.
Greetings,
next prev parent reply other threads:[~2024-08-02 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 21:19 [PATCH 0/2] io_uring: minor sqpoll code refactoring Olivier Langlois
2024-07-30 20:56 ` [PATCH 1/2] io_uring: micro optimization of __io_sq_thread() condition Olivier Langlois
2024-08-02 11:17 ` Pavel Begunkov
2024-07-30 21:10 ` [PATCH 2/2] io_uring: do the sqpoll napi busy poll outside the submission block Olivier Langlois
2024-08-02 11:14 ` Pavel Begunkov
2024-08-02 14:22 ` Olivier Langlois [this message]
2024-08-02 15:30 ` Pavel Begunkov
2024-08-02 13:11 ` (subset) [PATCH 0/2] io_uring: minor sqpoll code refactoring Jens Axboe
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=88b3d7be16b7e4fe788730347dd1b902a75423f0.camel@trillion01.com \
[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