From: Jakub Kicinski <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Linus Torvalds <[email protected]>,
io-uring <[email protected]>,
Olivier Langlois <[email protected]>
Subject: Re: [GIT PULL] io_uring updates for 5.18-rc1
Date: Sat, 26 Mar 2022 13:06:15 -0700 [thread overview]
Message-ID: <20220326130615.2d3c6c85@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <[email protected]>
On Sat, 26 Mar 2022 13:47:24 -0600 Jens Axboe wrote:
> On 3/26/22 1:28 PM, Jakub Kicinski wrote:
> > On Fri, 18 Mar 2022 15:59:16 -0600 Jens Axboe wrote:
> >> - Support for NAPI on sockets (Olivier)
> >
> > Were we CCed on these patches? I don't remember seeing them,
> > and looks like looks like it's inventing it's own constants
> > instead of using the config APIs we have.
>
> Don't know if it was ever posted on the netdev list
Hm, maybe I don't understand how things are supposed to work.
I'm surprised you're unfazed.
> but the patches have been discussed for 6-9 months on the io_uring
> list.
You may need explain to me how that's relevant :)
The point is the networking maintainers have not seen it.
> Which constants are you referring to? Only odd one I see is
> NAPI_TIMEOUT, other ones are using the sysctl bits. If we're
> missing something here, do speak up and we'll make sure it's
> consistent with the regular NAPI.
SO_BUSY_POLL_BUDGET, 8 is quite low for many practical uses.
I'd also like to have a conversation about continuing to use
the socket as a proxy for NAPI_ID, NAPI_ID is exposed to user
space now. io_uring being a new interface I wonder if it's not
better to let the user specify the request parameters directly.
> Adding Olivier who wrote the NAPI support.
>
next prev parent reply other threads:[~2022-03-26 20:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 21:59 [GIT PULL] io_uring updates for 5.18-rc1 Jens Axboe
2022-03-22 0:25 ` pr-tracker-bot
2022-03-26 19:28 ` Jakub Kicinski
2022-03-26 19:47 ` Jens Axboe
2022-03-26 20:06 ` Jakub Kicinski [this message]
2022-03-26 20:57 ` Jens Axboe
2022-03-26 21:06 ` Jens Axboe
2022-03-26 21:30 ` Jakub Kicinski
2022-03-30 23:30 ` Jakub Kicinski
2022-03-31 0:44 ` Jens Axboe
2022-06-01 6:59 ` Olivier Langlois
2022-06-01 16:24 ` Jakub Kicinski
2022-06-01 18:09 ` Linus Torvalds
2022-06-01 18:21 ` Jens Axboe
2022-06-01 18:28 ` Linus Torvalds
2022-06-01 18:34 ` Jens Axboe
2022-06-01 18:52 ` Linus Torvalds
2022-06-01 19:10 ` Jens Axboe
2022-06-01 19:20 ` Linus Torvalds
2022-08-16 15:53 ` Deprecation of IORING_OP_EPOLL_CTL (Re: [GIT PULL] io_uring updates for 5.18-rc1) Stefan Metzmacher
2022-06-01 8:01 ` [GIT PULL] io_uring updates for 5.18-rc1 Olivier Langlois
2022-06-01 6:58 ` Olivier Langlois
2022-06-01 6:58 ` Olivier Langlois
2022-06-01 17:04 ` Jakub Kicinski
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=20220326130615.2d3c6c85@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
[email protected] \
[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