mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tal Zussman <tz2294@columbia.edu>
To: Bernd Schubert <bernd@bsbernd.com>, Miklos Szeredi <miklos@szeredi.hu>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	fuse-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
	Joanne Koong <joannelkoong@gmail.com>
Subject: Re: [PATCH 0/2] fuse: convert the readdir cache to use folios
Date: Tue, 13 Oct 2026 15:20:23 -0400	[thread overview]
Message-ID: <81e07de2-ec8d-4ffb-bffd-44391ce9a2e3@columbia.edu> (raw)
In-Reply-To: <3b7a2fea-3fb9-42b6-aef2-d9770e3562d9@bsbernd.com>

On 10/13/26 2:13 PM, Bernd Schubert wrote:
> On 10/13/26 19:49, Tal Zussman wrote:
>> On 10/13/26 1:38 PM, Bernd Schubert wrote:
>>> On 10/13/26 18:48, Tal Zussman wrote:
>>>> On 9/24/26 7:42 PM, Tal Zussman wrote:
>>>>> Convert the readdir cache lookups in fs/fuse/readdir.c to folios. This
>>>>> removes the last caller of find_get_page_flags() and one of the last
>>>>> callers of find_lock_page().
>>>>>
>>>>> Based on fuse/for-next.
>>>>>
>>>>
>>>> Hi,
>>>>
>>>> Following up on this. It'd be great to get this in as it would allow us
>>>> to remove find_get_page_flags() and find_lock_page() next cycle.
>>>
>>>
>>> fuse has large folios enabled now - the patches need to handle that.
>>> Even if it would not be enabled yet, Joanne had spend quite some effort
>>> to enable large folios, any change that tried to rely on behavior would
>>> have just increased her burden...
>>>
>> Hi Bernd,
>> 
>> As far as I can see, Joanne's patches enable large folios for regular files.
>> Here we operate on directories, which are initialized through fuse_init_dir()
>> and so do not use large folios. In any case, these patches switch to using
>> the relevant folio helpers, which would get us closer to using large folios
>> in the readdir cache if that's eventually desired.
> 
> Hi Tal,
> 
> oops, sorry, I was bailing out when I read it as "this introduces
> another stop gap for large folios". I quickly scanned over it, but don't
> have much time right now - will review tomorrow morning.
> 
> 
> Sorry again,
> Bernd
> 

No problem, thanks!



  reply	other threads:[~2026-10-13 19:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 23:42 Tal Zussman
2026-09-24 23:42 ` [PATCH 1/2] fuse: convert fuse_add_dirent_to_cache() " Tal Zussman
2026-09-24 23:42 ` [PATCH 2/2] fuse: convert fuse_readdir_cached() " Tal Zussman
2026-10-13 16:48 ` [PATCH 0/2] fuse: convert the readdir cache " Tal Zussman
2026-10-13 17:38   ` Bernd Schubert
2026-10-13 17:49     ` Tal Zussman
2026-10-13 18:13       ` Bernd Schubert
2026-10-13 19:20         ` Tal Zussman [this message]
2026-10-15 13:46 ` Miklos Szeredi

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=81e07de2-ec8d-4ffb-bffd-44391ce9a2e3@columbia.edu \
    --to=tz2294@columbia.edu \
    --cc=bernd@bsbernd.com \
    --cc=fuse-devel@lists.linux.dev \
    --cc=joannelkoong@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=willy@infradead.org \
    /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

all inboxes | Powered by JetHome®