From: Olivier Langlois <[email protected]>
To: Pavel Begunkov <[email protected]>,
Jens Axboe <[email protected]>,
[email protected]
Subject: Re: [PATCH] io_uring: add napi busy settings to the fdinfo output
Date: Tue, 30 Jul 2024 10:04:43 -0400 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Thank you Pavel for your review!
Since I have no indication if Jens did see your comment before applying
my patch, I will prepare another one with your comment addressed.
just ignore it if it is not needed anymore.
On Tue, 2024-07-30 at 12:05 +0100, Pavel Begunkov wrote:
> On 7/29/24 23:38, Olivier Langlois wrote:
> > this info may be useful when attempting to debug a problem
> > involving a ring using the feature.
>
> Apart from a comment below,
>
> Reviewed-by: Pavel Begunkov <[email protected]>
>
> Maybe, Jens would be willing to move the block after the spin_unlock
> while applying.
>
>
> > Signed-off-by: Olivier Langlois <[email protected]>
> > ---
> > io_uring/fdinfo.c | 13 ++++++++++++-
> > 1 file changed, 12 insertions(+), 1 deletion(-)
> >
> > diff --git a/io_uring/fdinfo.c b/io_uring/fdinfo.c
> > index b1e0e0d85349..3ba42e136a40 100644
> > --- a/io_uring/fdinfo.c
> > +++ b/io_uring/fdinfo.c
> > @@ -221,7 +221,18 @@ __cold void io_uring_show_fdinfo(struct
> > seq_file *m, struct file *file)
> > cqe->user_data, cqe->res, cqe->flags);
> >
> > }
> > -
> > +#ifdef CONFIG_NET_RX_BUSY_POLL
> > + if (ctx->napi_enabled) {
> > + seq_puts(m, "NAPI:\tenabled\n");
> > + seq_printf(m, "napi_busy_poll_dt:\t%llu\n", ctx-
> > >napi_busy_poll_dt);
> > + if (ctx->napi_prefer_busy_poll)
> > + seq_puts(m,
> > "napi_prefer_busy_poll:\ttrue\n");
> > + else
> > + seq_puts(m,
> > "napi_prefer_busy_poll:\tfalse\n");
> > + } else {
> > + seq_puts(m, "NAPI:\tdisabled\n");
> > + }
> > +#endif
> > spin_unlock(&ctx->completion_lock);
>
> That doesn't need to be under completion_lock, it should move outside
> of the spin section.
>
>
> > }
> > #endif
>
next prev parent reply other threads:[~2024-07-30 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 22:38 [PATCH] io_uring: add napi busy settings to the fdinfo output Olivier Langlois
2024-07-30 11:05 ` Pavel Begunkov
2024-07-30 14:04 ` Olivier Langlois [this message]
2024-07-30 14:08 ` Pavel Begunkov
2024-07-30 14:46 ` Jens Axboe
2024-07-30 12:26 ` Jens Axboe
2024-07-30 15:33 ` Pavel Begunkov
2024-07-30 15:38 ` Pavel Begunkov
2024-07-30 19:05 ` Olivier Langlois
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=0ad8d8b1912f5d3b1115dca9ee229c6f6c0226b2.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