From: Jens Axboe <[email protected]>
To: [email protected]
Subject: [PATCHSET v2 0/3] Provided buffer improvements
Date: Thu, 10 Mar 2022 09:59:04 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
One functional improvement for recycling provided buffers when we don't
know when the readiness trigger comes in, one optimization for how
we index them, and one fix for READ/READV on re-selecting a buffer
when we attempt to issue the request.
--
Jens Axboe
next reply other threads:[~2022-03-10 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 16:59 Jens Axboe [this message]
2022-03-10 16:59 ` [PATCH 1/3] io_uring: retry early for reads if we can poll Jens Axboe
2022-03-10 16:59 ` [PATCH 2/3] io_uring: ensure reads re-import for selected buffers Jens Axboe
2022-03-10 16:59 ` [PATCH 3/3] io_uring: recycle provided buffers if request goes async 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] \
/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