From: Miklos Szeredi <miklos@szeredi.hu>
To: Chad Austin <chadaustin@fb.com>
Cc: linux-fsdevel@vger.kernel.org, chad@chadaustin.me
Subject: Re: [PATCH] fuse: cache readdir calls if filesystem opts out of opendir
Date: Mon, 4 Feb 2019 08:43:35 +0100 [thread overview]
Message-ID: <CAJfpegswEXJAk3GBuvcectUTTsFMXgGJ5qsZseP6JQqs2EuZxQ@mail.gmail.com> (raw)
In-Reply-To: <20190129003434.316288-1-chadaustin@fb.com>
On Tue, Jan 29, 2019 at 1:34 AM Chad Austin <chadaustin@fb.com> wrote:
>
> If a filesystem returns ENOSYS from opendir and thus opts out of
> opendir and releasedir requests, it almost certainly would also like
> readdir results cached. Default open_flags to FOPEN_KEEP_CACHE and
> FOPEN_CACHE_DIR in that case.
>
> With this patch, I've measured recursive directory enumeration across
> large FUSE mounts to be faster than native mounts.
>
> Signed-off-by: Chad Austin <chadaustin@fb.com>
Thanks, applied.
Miklos
prev parent reply other threads:[~2019-02-04 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 0:34 [PATCH] fuse: cache readdir calls if filesystem opts out of opendir Chad Austin
2019-02-04 7:43 ` Miklos Szeredi [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=CAJfpegswEXJAk3GBuvcectUTTsFMXgGJ5qsZseP6JQqs2EuZxQ@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=chad@chadaustin.me \
--cc=chadaustin@fb.com \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).