From: Joanne Koong <joannelkoong@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, bernd.schubert@fastmail.fm,
jlayton@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v2] fuse: use splice for reading user pages on servers that enable it
Date: Mon, 12 May 2025 12:03:26 -0700 [thread overview]
Message-ID: <CAJnrk1ZXBOzMB69vyhzpqZWdSmpSxRcJuirVBVmPd6ynemt_SQ@mail.gmail.com> (raw)
In-Reply-To: <CAJfpegsc8OHkv8wQrHSxXE-5Tq8DMhNnGWVpSnpu5+z5PBghFA@mail.gmail.com>
On Wed, May 7, 2025 at 7:45 AM Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> On Wed, 23 Apr 2025 at 01:56, Joanne Koong <joannelkoong@gmail.com> wrote:
>
> > For servers that do not need to access pages after answering the
> > request, splice gives a non-trivial improvement in performance.
> > Benchmarks show roughly a 40% speedup.
>
> Hmm, have you looked at where this speedup comes from?
>
> Is this a real zero-copy scenario where the server just forwards the
> pages to a driver which does DMA, so that the CPU never actually
> touches the page contents?
I ran the benchmarks last month on the passthrough_ll server (from the
libfuse examples) with the actual copying out / buffer processing
removed (eg the .write_buf handler immediately returns
"fuse_reply_write(req, fuse_buf_size(in_buf));".
Thanks,
Joanne
>
> Thanks,
> Miklos
next prev parent reply other threads:[~2025-05-12 19:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 23:56 [PATCH v2] fuse: use splice for reading user pages on servers that enable it Joanne Koong
2025-05-02 13:16 ` Bernd Schubert
2025-05-07 14:45 ` Miklos Szeredi
2025-05-12 19:03 ` Joanne Koong [this message]
2025-05-13 5:46 ` Miklos Szeredi
2025-05-13 21:29 ` Joanne Koong
2025-05-14 11:56 ` Miklos Szeredi
2025-05-14 23:17 ` Joanne Koong
2025-05-15 8:38 ` Miklos Szeredi
2025-05-15 19:16 ` Joanne Koong
2025-05-16 7:58 ` Miklos Szeredi
2025-05-16 18:15 ` Bernd Schubert
2025-05-16 23:38 ` 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=CAJnrk1ZXBOzMB69vyhzpqZWdSmpSxRcJuirVBVmPd6ynemt_SQ@mail.gmail.com \
--to=joannelkoong@gmail.com \
--cc=bernd.schubert@fastmail.fm \
--cc=jlayton@kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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;
as well as URLs for NNTP newsgroup(s).