From: Bernd Schubert <bernd@bsbernd.com>
To: Miklos Szeredi <miklos@szeredi.hu>, Bernd Schubert <bschubert@ddn.com>
Cc: "Matthew R. Ochs" <mochs@nvidia.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Joanne Koong <joannelkoong@gmail.com>
Subject: Re: [PATCH v2] fuse: back uncached readdir buffers with pages
Date: Wed, 29 Apr 2026 12:47:58 +0200 [thread overview]
Message-ID: <977f4a2a-5337-449e-b34a-68a128a894da@bsbernd.com> (raw)
In-Reply-To: <CAJfpegti_MFgBie0=gX0RfZ7yQTtfzUMaUk6o+qunO9cuOeE4A@mail.gmail.com>
On 4/29/26 12:38, Miklos Szeredi wrote:
> On Wed, 29 Apr 2026 at 11:29, Bernd Schubert <bschubert@ddn.com> wrote:
>
>> Josef and Joanne had spent quite some time to allow to use large folios
>> - maybe we should make use of it? Attached is a totally untested patch
>> and that ignores all of Miklos' comments for now. Also cannot be that
>> easily back ported
>
> I'd be happier if the VM infrastructure for folio arrays was available
> first, then used in fuse. Not the other way round.
It is only the the missing vm_map part for folios? I had found a patch
https://lists.freedesktop.org/archives/dri-devel/2025-March/497993.html
and added the comment therefore. Maybe we can bring it up with Matthew
or someone else from mm next week.
A bit a pity if there is generic support for large folios and fuse
internals for random reasons then still use single pages.
Thanks,
Bernd
prev parent reply other threads:[~2026-04-29 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 23:29 [PATCH v2] fuse: back uncached readdir buffers with pages Matthew R. Ochs
2026-04-29 7:27 ` Miklos Szeredi
2026-04-30 19:24 ` Matt Ochs
2026-04-29 9:29 ` Bernd Schubert
2026-04-29 10:38 ` Miklos Szeredi
2026-04-29 10:47 ` Bernd Schubert [this message]
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=977f4a2a-5337-449e-b34a-68a128a894da@bsbernd.com \
--to=bernd@bsbernd.com \
--cc=bschubert@ddn.com \
--cc=joannelkoong@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mochs@nvidia.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