From: Dharmendra Singh <dharamhans87@gmail.com>
To: miklos@szeredi.hu
Cc: Dharmendra Singh <dharamhans87@gmail.com>,
linux-fsdevel@vger.kernel.org, fuse-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] FUSE: Implement atomic lookup + open
Date: Tue, 22 Mar 2022 17:21:46 +0530 [thread overview]
Message-ID: <20220322115148.3870-1-dharamhans87@gmail.com> (raw)
In FUSE, as of now, uncached lookups are expensive over the wire.
E.g additional latencies and stressing (meta data) servers from
thousands of clients. These lookup calls possibly can be avoided
in some cases. Incoming two patches addresses this issue.
First patch handles the case where we open first time a file/dir or create
a file (O_CREAT) but do a lookup first on it. After lookup is performed
we make another call into libfuse to open the file. Now these two separate
calls into libfuse can be combined and performed as a single call into
libfuse.
Second patch handles the case when we are opening an already existing file
(positive dentry). Before this open call, we re-validate the inode and
this re-validation does a lookup on the file and verify the inode.
This separate lookup also can be avoided (for non-dir) and combined
with open call into libfuse.
Here is the link to the libfuse pull request which implements atomic open
https://github.com/libfuse/libfuse/pull/644
I am going to post performance results shortly.
Dharmendra Singh (2):
FUSE: Implement atomic lookup + open
FUSE: Avoid lookup in d_revalidate()
fs/fuse/dir.c | 179 +++++++++++++++++++++++++++++++++-----
fs/fuse/file.c | 30 ++++++-
fs/fuse/fuse_i.h | 13 ++-
fs/fuse/inode.c | 4 +-
fs/fuse/ioctl.c | 2 +-
include/uapi/linux/fuse.h | 2 +
6 files changed, 204 insertions(+), 26 deletions(-)
--
2.17.1
next reply other threads:[~2022-03-22 11:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 11:51 Dharmendra Singh [this message]
2022-03-22 11:51 ` [PATCH v2 1/2] FUSE: Implement atomic lookup + open Dharmendra Singh
2022-04-22 15:29 ` Miklos Szeredi
2022-04-25 5:25 ` Dharmendra Hans
2022-04-25 7:37 ` Miklos Szeredi
2022-04-25 10:43 ` Dharmendra Hans
2022-04-29 4:34 ` Dharmendra Hans
2022-03-22 11:51 ` [PATCH v2 2/2] FUSE: Avoid lookup in d_revalidate() Dharmendra Singh
2022-03-22 12:12 ` [PATCH v2 0/2] FUSE: Atomic lookup + open performance numbers Dharmendra Singh
2022-03-29 11:07 ` [PATCH v2 0/2] FUSE: Implement atomic lookup + open Dharmendra Hans
2022-04-07 9:57 ` Dharmendra Hans
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=20220322115148.3870-1-dharamhans87@gmail.com \
--to=dharamhans87@gmail.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).