From: Paulo Alcantara <pc@manguebit.com>
To: Shyam Prasad N <nspmangalore@gmail.com>
Cc: Benjamin Coddington <bcodding@redhat.com>,
Amir Goldstein <amir73il@gmail.com>,
lsf-pc@lists.linux-foundation.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-mm@kvack.org, brauner@kernel.org,
Matthew Wilcox <willy@infradead.org>,
David Howells <dhowells@redhat.com>,
Jeff Layton <jlayton@redhat.com>,
Steve French <smfrench@gmail.com>,
trondmy@kernel.org, Shyam Prasad N <sprasad@microsoft.com>
Subject: Re: [LSF/MM/BPF TOPIC] Predictive readahead of dentries
Date: Wed, 15 Jan 2025 11:47:58 -0300 [thread overview]
Message-ID: <ea554f398a1d263ea06c02c8601cbb1b@manguebit.com> (raw)
In-Reply-To: <CANT5p=r1t5hG9jQ8Py1VkvkNFxLJpGUXimxVBTR=ApqEFWL6hA@mail.gmail.com>
Shyam Prasad N <nspmangalore@gmail.com> writes:
> We load the dentry cache with results of QueryDirectory. But what I'm
> proposing here is a read ahead, even before the next readdir is done
> by the application. i.e. the idea is that the data necessary to emit
> dentries is already in the cache before it is even called. That should
> speed up the overall directory reads.
Thanks for the explanation.
We'd need to be careful as in CIFS we could end up with several
automounts (DFS links) by doing these readdirs in advance, especially on
slow connections and when failover happens when mounting them.
next prev parent reply other threads:[~2025-01-15 14:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 3:38 Shyam Prasad N
2025-01-14 12:39 ` [Lsf-pc] " Jan Kara
2025-01-15 9:52 ` Shyam Prasad N
2025-01-14 13:24 ` Amir Goldstein
2025-01-14 14:12 ` Benjamin Coddington
2025-01-14 15:01 ` Paulo Alcantara
2025-01-15 14:30 ` Shyam Prasad N
2025-01-15 14:47 ` Paulo Alcantara [this message]
2025-01-15 11:27 ` Shyam Prasad N
2025-01-15 14:21 ` Amir Goldstein
2025-01-20 21:26 ` Benjamin Coddington
2025-01-14 15:59 ` James Bottomley
2025-01-16 4:50 ` Al Viro
2025-01-16 5:31 ` Christoph Hellwig
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=ea554f398a1d263ea06c02c8601cbb1b@manguebit.com \
--to=pc@manguebit.com \
--cc=amir73il@gmail.com \
--cc=bcodding@redhat.com \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=nspmangalore@gmail.com \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.com \
--cc=trondmy@kernel.org \
--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