From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH for-next 0/2] random for-next io_uring patches
Date: Fri, 25 Nov 2022 06:13:38 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, 24 Nov 2022 19:46:39 +0000, Pavel Begunkov wrote:
> 1/2 removes two spots io_req_complete_post() in favour of the generic
> infra. 2/2 inlines io_cq_unlock_post() back.
>
> Pavel Begunkov (2):
> io_uring: don't use complete_post in kbuf
> io_uring: keep unlock_post inlined in hot path
>
> [...]
Applied, thanks!
[1/2] io_uring: don't use complete_post in kbuf
commit: c3b490930dbe6a6c98d3820f445757ddec1efb08
[2/2] io_uring: keep unlock_post inlined in hot path
commit: 5d772916855f593672de55c437925daccc8ecd73
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-11-25 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 19:46 [PATCH for-next 0/2] random for-next io_uring patches Pavel Begunkov
2022-11-24 19:46 ` [PATCH for-next 1/2] io_uring: don't use complete_post in kbuf Pavel Begunkov
2022-11-24 19:46 ` [PATCH for-next 2/2] io_uring: keep unlock_post inlined in hot path Pavel Begunkov
2022-11-25 13:13 ` 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=166938201833.7977.10828326653350936954.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