From: Jakub Kicinski <kuba@kernel.org>
To: Stefan Roesch <shr@devkernel.io>
Cc: kernel-team@fb.com, axboe@kernel.dk, olivier@trillion01.com,
netdev@vger.kernel.org, io-uring@vger.kernel.org
Subject: Re: [RFC PATCH v3 0/3] io_uring: add napi busy polling support
Date: Wed, 16 Nov 2022 10:31:17 -0800 [thread overview]
Message-ID: <20221116103117.6b82e982@kernel.org> (raw)
In-Reply-To: <20221115070900.1788837-1-shr@devkernel.io>
On Mon, 14 Nov 2022 23:08:57 -0800 Stefan Roesch wrote:
> This adds the napi busy polling support in io_uring.c. It adds a new
> napi_list to the io_ring_ctx structure. This list contains the list of
> napi_id's that are currently enabled for busy polling. This list is
> used to determine which napi id's enabled busy polling.
>
> To set the new napi busy poll timeout, a new io-uring api has been
> added. It sets the napi busy poll timeout for the corresponding ring.
>
> There is also a corresponding liburing patch series, which enables this
> feature. The name of the series is "liburing: add add api for napi busy
> poll timeout". It also contains two programs to test the this.
>
> Testing has shown that the round-trip times are reduced to 38us from
> 55us by enabling napi busy polling with a busy poll timeout of 100us.
Acked-by: Jakub Kicinski <kuba@kernel.org>
Thanks!
next prev parent reply other threads:[~2022-11-16 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 7:08 [RFC PATCH v3 0/3] io_uring: add napi busy polling support Stefan Roesch
2022-11-15 7:08 ` [RFC PATCH v3 1/3] " Stefan Roesch
2022-11-15 7:08 ` [RFC PATCH v3 2/3] io_uring: add api to set napi busy poll timeout Stefan Roesch
2022-11-16 19:05 ` Jens Axboe
2022-11-15 7:09 ` [RFC PATCH v3 3/3] io_uring: add api to set napi prefer busy poll Stefan Roesch
2022-11-16 18:31 ` Jakub Kicinski [this message]
2022-11-16 18:44 ` [RFC PATCH v3 0/3] io_uring: add napi busy polling support Jens Axboe
2022-11-16 20:09 ` Jakub Kicinski
2022-11-16 20:12 ` 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=20221116103117.6b82e982@kernel.org \
--to=kuba@kernel.org \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=olivier@trillion01.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.