From: Jakub Kicinski <[email protected]>
To: Olivier Langlois <[email protected]>
Cc: Jens Axboe <[email protected]>,
Linus Torvalds <[email protected]>,
io-uring <[email protected]>
Subject: Re: [GIT PULL] io_uring updates for 5.18-rc1
Date: Wed, 1 Jun 2022 10:04:56 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Wed, 01 Jun 2022 02:58:25 -0400 Olivier Langlois wrote:
> On Sat, 2022-03-26 at 12:28 -0700, 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.
>
> No, you werent CCed on those patches. No one, including myself, did
> think that you would want to review code not in your subsystem and
> running scripts/get_maintainer.pl on the patch did not list your group.
> If not receiving an invitation did upset you, I am sorry. This was not
> intentional
All the talk about teams, groups and APIs. Like EXPORT_SYMBOL() is
supposed to be about crossing organizational boundaries.
Seems pretty obvious to me that netdev people and authors of the
original busy polling may have guidance and advice on networking uAPIs.
Maybe thinking more open and collaborative approach leads to better
results is naive. I'm certainly not trying to mark the territory or
anything like that.
> Can you be more explicit about the constants and the config API you are
> refering to?
I think I was talking about the setsockopts which can be used to modify
the polling parameters. I'm not 100% sure now, it was 2 months ago.
prev parent reply other threads:[~2022-06-01 17:05 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
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 [this message]
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 \
[email protected] \
[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