From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Subject: Re: [PATCH for-next] io_uring/zc: notification completion optimisation
Date: Tue, 26 Jul 2022 12:29:51 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <9e010125175e80baf51f0ca63bdc7cc6a4a9fa56.1658838783.git.asml.silence@gmail.com>
On Tue, 26 Jul 2022 14:06:29 +0100, Pavel Begunkov wrote:
> We want to use all optimisations that we have for io_uring requests like
> completion batching, memory caching and more but for zc notifications.
> Fortunately, notification perfectly fit the request model so we can
> overlay them onto struct io_kiocb and use all the infratructure.
>
> Most of the fields of struct io_notif natively fits into io_kiocb, so we
> replace struct io_notif with struct io_kiocb carrying struct
> io_notif_data in the cmd cache line. Then we adapt io_alloc_notif() to
> use io_alloc_req()/io_alloc_req_refill(), and kill leftovers of hand
> coded caching. __io_notif_complete_tw() is converted to use io_uring's
> tw infra.
>
> [...]
Applied, thanks!
[1/1] io_uring/zc: notification completion optimisation
commit: fbe6f6bc3210e853aab74f20da776c15c5b052fe
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-07-26 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 13:06 [PATCH for-next] io_uring/zc: notification completion optimisation Pavel Begunkov
2022-07-26 18:29 ` 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=165886019187.1523978.7573816236813433809.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