From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: [RFC v2 0/2] non-atomic req->refs
Date: Thu, 29 Apr 2021 18:20:40 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
[knowingly buggy, don't use]
Just a glimpse on the de-atomising request refcounting for benchmarking,
dirty and with a bunch of known problems (in [a]poll and iopoll).
Haven't got any perf numbers myself yet.
v2: wrong patch with inverted an req_ref_sub_and_test() condition
Pavel Begunkov (2):
io_uring: defer submission ref put
io_uring: non-atomic request refs
fs/io_uring.c | 99 ++++++++++++++++++++++++++++++---------------------
1 file changed, 58 insertions(+), 41 deletions(-)
--
2.31.1
next reply other threads:[~2021-04-29 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 17:20 Pavel Begunkov [this message]
2021-04-29 17:20 ` [PATCH v2 1/2] io_uring: defer submission ref put Pavel Begunkov
2021-04-29 17:20 ` [PATCH v2 2/2] io_uring: non-atomic request refs Pavel Begunkov
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] \
/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