From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: [RFC 0/2] kvmalloc reg file table
Date: Sat, 19 Jun 2021 00:32:15 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
As mentioned before, couldn't get numbers due to huge performance
jumps between reboots outweighting any gains of this series, so
sending just as an RFC.
Jens, sorry for pestering, but if you will be doing benchmarking,
can you compare how it is with the 1/2?
2/2 clearly slashes some extra cycles.
Pavel Begunkov (2):
io_uring: use kvmalloc for fixed files
io_uring: inline fixed part of io_file_get()
fs/io_uring.c | 98 +++++++++++++++++++++++++--------------------------
1 file changed, 49 insertions(+), 49 deletions(-)
--
2.31.1
next reply other threads:[~2021-06-18 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 23:32 Pavel Begunkov [this message]
2021-06-18 23:32 ` [PATCH 1/2] io_uring: use kvmalloc for fixed files Pavel Begunkov
2021-06-18 23:32 ` [PATCH 2/2] io_uring: inline fixed part of io_file_get() 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