From: Jakub Kicinski <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Gabriel Krisman Bertazi <[email protected]>,
[email protected], [email protected]
Subject: Re: [PATCH v2 1/4] net: Split a __sys_bind helper for io_uring
Date: Wed, 19 Jun 2024 08:04:47 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Wed, 19 Jun 2024 07:40:40 -0600 Jens Axboe wrote:
> On 6/18/24 6:49 PM, Jakub Kicinski wrote:
> > On Fri, 14 Jun 2024 12:30:44 -0400 Gabriel Krisman Bertazi wrote:
> >> io_uring holds a reference to the file and maintains a
> >> sockaddr_storage address. Similarly to what was done to
> >> __sys_connect_file, split an internal helper for __sys_bind in
> >> preparation to supporting an io_uring bind command.
> >>
> >> Reviewed-by: Jens Axboe <[email protected]>
> >> Signed-off-by: Gabriel Krisman Bertazi <[email protected]>
> >
> > Acked-by: Jakub Kicinski <[email protected]>
>
> Are you fine with me queueing up 1-2 via the io_uring branch?
> I'm guessing the risk of conflict should be very low, so doesn't
> warrant a shared branch.
Yup, exactly, these can go via io_uring without branch juggling.
next prev parent reply other threads:[~2024-06-19 15:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 16:30 [PATCH v2 1/4] net: Split a __sys_bind helper for io_uring Gabriel Krisman Bertazi
2024-06-14 16:30 ` [PATCH v2 2/4] net: Split a __sys_listen " Gabriel Krisman Bertazi
2024-06-14 22:44 ` Kuniyuki Iwashima
2024-06-19 0:50 ` Jakub Kicinski
2024-06-14 16:30 ` [PATCH v2 3/4] io_uring: Introduce IORING_OP_BIND Gabriel Krisman Bertazi
2024-06-14 22:46 ` Kuniyuki Iwashima
2024-06-15 0:27 ` Jens Axboe
2024-06-14 16:30 ` [PATCH v2 4/4] io_uring: Introduce IORING_OP_LISTEN Gabriel Krisman Bertazi
2024-06-14 22:42 ` [PATCH v2 1/4] net: Split a __sys_bind helper for io_uring Kuniyuki Iwashima
2024-06-19 0:49 ` Jakub Kicinski
2024-06-19 13:40 ` Jens Axboe
2024-06-19 15:04 ` Jakub Kicinski [this message]
2024-06-19 15:06 ` Jens Axboe
2024-07-15 12:49 ` Matus Jokay
2024-07-15 13:59 ` Tetsuo Handa
2024-07-22 12:37 ` Matus Jokay
2024-06-19 14: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 \
[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