From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Subject: Re: [PATCH for-next v2 0/2] notification optimisation
Date: Wed, 27 Jul 2022 09:01:28 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Wed, 27 Jul 2022 10:30:39 +0100, Pavel Begunkov wrote:
> Reuse request infra for zc notifications for optimisation and also
> a nice line count reduction.
>
> v2:
> add missing patch exporting io_alloc_req()
>
> Pavel Begunkov (2):
> io_uring: export req alloc from core
> io_uring: notification completion optimisation
>
> [...]
Applied, thanks!
[1/2] io_uring: export req alloc from core
commit: bd1a3783dd749012134b142b52e5704f7c142897
[2/2] io_uring: notification completion optimisation
commit: 14b146b688ad9593f5eee93d51a34d09a47e50b5
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-07-27 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 9:30 [PATCH for-next v2 0/2] notification optimisation Pavel Begunkov
2022-07-27 9:30 ` [PATCH for-next v2 1/2] io_uring: export req alloc from core Pavel Begunkov
2022-07-27 9:30 ` [PATCH for-next v2 2/2] io_uring: notification completion optimisation Pavel Begunkov
2022-07-27 15:01 ` Jens Axboe [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 \
--in-reply-to=165893408881.1575345.16179131735370544476.b4-ty@kernel.dk \
[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