From: Xiaobing Li <xiaobing.li@samsung.com>
To: joannelkoong@gmail.com
Cc: asml.silence@gmail.com, axboe@kernel.dk, bschubert@ddn.com,
io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org,
miklos@szeredi.hu, joshi.k@samsung.com, kun.dou@samsung.com,
peiwei.li@samsung.com, xue01.he@samsung.com
Subject: Re: [PATCH v1 0/2] fuse io_uring: support registered buffers
Date: Thu, 23 Oct 2025 11:45:24 +0000 [thread overview]
Message-ID: <20251023114524.1052805-1-xiaobing.li@samsung.com> (raw)
In-Reply-To: <20251022202021.3649586-1-joannelkoong@gmail.com>
On 10/22/25 22:20, Joanne Koong wrote:
> This adds support for daemons who preregister buffers to minimize the overhead
> of pinning/unpinning user pages and translating virtual addresses. Registered
> buffers pay the cost once during registration then reuse the pre-pinned pages,
> which helps reduce the per-op overhead.
>
> This is on top of commit 211ddde0823f in the iouring tree.
Do you have any test data? How does the benefit compare?
By the way, how were the changes made to libfuse?
Thanks,
Xiaobing Li
next prev parent reply other threads:[~2025-10-24 6:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 20:20 [PATCH v1 0/2] fuse io_uring: support registered buffers Joanne Koong
2025-10-22 20:20 ` [PATCH v1 1/2] io-uring: add io_uring_cmd_get_buffer_info() Joanne Koong
2025-10-23 3:16 ` Caleb Sander Mateos
2025-10-23 22:20 ` Joanne Koong
2025-10-24 0:00 ` Joanne Koong
2025-10-22 20:20 ` [PATCH v1 2/2] fuse: support io-uring registered buffers Joanne Koong
2025-10-23 3:22 ` Caleb Sander Mateos
2025-10-23 12:39 ` kernel test robot
2025-10-23 13:22 ` kernel test robot
2025-10-23 17:42 ` Joanne Koong
2025-10-23 23:44 ` Joanne Koong
2025-10-22 20:43 ` [PATCH v1 0/2] fuse io_uring: support " Bernd Schubert
2025-10-23 22:27 ` Joanne Koong
2025-10-24 18:12 ` Bernd Schubert
2025-10-24 19:37 ` Joanne Koong
[not found] ` <CGME20251023114956epcas5p33a9384d06985dc5936fd355f1d580fb2@epcas5p3.samsung.com>
2025-10-23 11:45 ` Xiaobing Li [this message]
2025-10-24 18:02 ` Joanne Koong
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=20251023114524.1052805-1-xiaobing.li@samsung.com \
--to=xiaobing.li@samsung.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=bschubert@ddn.com \
--cc=io-uring@vger.kernel.org \
--cc=joannelkoong@gmail.com \
--cc=joshi.k@samsung.com \
--cc=kun.dou@samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=peiwei.li@samsung.com \
--cc=xue01.he@samsung.com \
/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