From: Olivier Langlois <olivier@trillion01.com>
To: Jens Axboe <axboe@kernel.dk>, Stefan Roesch <shr@devkernel.io>,
io-uring@vger.kernel.org, kernel-team@fb.com
Cc: ammarfaizi2@gnuweeb.org, netdev@vger.kernel.org, kuba@kernel.org
Subject: Re: [PATCH v15 0/7] io_uring: add napi busy polling support
Date: Wed, 31 Jan 2024 00:30:40 -0500 [thread overview]
Message-ID: <9a8748183fcecbe44406e93e47c47c1639871bfa.camel@trillion01.com> (raw)
In-Reply-To: <2b238cec-ab1b-4160-8fb0-ad199e1d0306@kernel.dk>
On Tue, 2024-01-30 at 15:59 -0700, Jens Axboe wrote:
> On 1/30/24 2:20 PM, Olivier Langlois wrote:
> > Hi,
> >
> > I was wondering what did happen to this patch submission...
> >
> > It seems like Stefan did put a lot of effort in addressing every
> > reported issue for several weeks/months...
> >
> > and then nothing... as if this patch has never been reviewed by
> > anyone...
> >
> > has it been decided to not integrate NAPI busy looping in io_uring
> > privately finally?
>
> It's really just waiting for testing, I want to ensure it's working
> as
> we want it to before committing. But the production bits I wanted to
> test on have been dragging out, hence I have not made any moves
> towards
> merging this for upstream just yet.
>
> FWIW, I have been maintaining the patchset, you can find the current
> series here:
>
> https://git.kernel.dk/cgit/linux/log/?h=io_uring-napi
>
Hi Jens,
ok thx for the update... Since I am a big user of the io_uring napi
busy polling, testing the official patchset is definitely something
that I can do to help...
I should be able to report back the result of my testing in few days!
next prev parent reply other threads:[~2024-01-31 5:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 16:38 [PATCH v15 0/7] io_uring: add napi busy polling support Stefan Roesch
2023-06-08 16:38 ` [PATCH v15 1/7] net: split off __napi_busy_poll from napi_busy_poll Stefan Roesch
2023-06-08 19:33 ` kernel test robot
2023-06-08 16:38 ` [PATCH v15 2/7] net: add napi_busy_loop_rcu() Stefan Roesch
2023-06-08 16:38 ` [PATCH v15 3/7] io-uring: move io_wait_queue definition to header file Stefan Roesch
2023-06-08 16:38 ` [PATCH v15 4/7] io-uring: add napi busy poll support Stefan Roesch
2023-06-08 16:38 ` [PATCH v15 5/7] io-uring: add sqpoll support for napi busy poll Stefan Roesch
2023-06-08 16:38 ` [PATCH v15 6/7] io_uring: add register/unregister napi function Stefan Roesch
2023-06-08 16:38 ` [PATCH v15 7/7] io_uring: add prefer busy poll to register and unregister napi api Stefan Roesch
2024-01-30 21:20 ` [PATCH v15 0/7] io_uring: add napi busy polling support Olivier Langlois
2024-01-30 22:59 ` Jens Axboe
2024-01-31 5:30 ` Olivier Langlois [this message]
2024-01-31 17:22 ` Olivier Langlois
2024-01-31 17:32 ` Jens Axboe
2024-01-31 17:59 ` Olivier Langlois
2024-01-31 19:56 ` Olivier Langlois
2024-01-31 20:52 ` Jens Axboe
2024-01-31 21:03 ` Olivier Langlois
2024-02-02 20:20 ` Olivier Langlois
2024-02-02 22:58 ` 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=9a8748183fcecbe44406e93e47c47c1639871bfa.camel@trillion01.com \
--to=olivier@trillion01.com \
--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=shr@devkernel.io \
/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).