From: Pavel Begunkov <asml.silence@gmail.com>
To: Olivier Langlois <olivier@trillion01.com>,
Jens Axboe <axboe@kernel.dk>,
io-uring@vger.kernel.org
Subject: Re: [PATCH] io_uring: add napi busy settings to the fdinfo output
Date: Tue, 30 Jul 2024 15:08:04 +0100 [thread overview]
Message-ID: <0de84f6b-bf13-4c96-9788-1089d4c3a959@gmail.com> (raw)
In-Reply-To: <0ad8d8b1912f5d3b1115dca9ee229c6f6c0226b2.camel@trillion01.com>
On 7/30/24 15:04, Olivier Langlois wrote:
> 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.
Jens saw it
https://git.kernel.dk/cgit/linux-block/commit/?h=for-6.12/io_uring
--
Pavel Begunkov
next prev parent reply other threads:[~2024-07-30 14:07 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
2024-07-30 14:08 ` Pavel Begunkov [this message]
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=0de84f6b-bf13-4c96-9788-1089d4c3a959@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@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