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, bschubert@ddn.com
Subject: [PATCH v4 0/3] FUSE: Implement atomic lookup + open/create
Date: Mon, 2 May 2022 15:55:18 +0530 [thread overview]
Message-ID: <20220502102521.22875-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 three patches address this issue.
Fist patch handles the case where we are creating a file with O_CREAT.
Before we go for file creation, we do a lookup on the file which is most
likely non-existent. After this lookup is done, we again go into libfuse
to create file. Such lookups where file is most likely non-existent, can
be avoided.
Second patch handles the case where we open first time a file/dir
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.
Third 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. After open returns we can revalidate the inode.
This optimisation is performed only when we do not have default permissions
enabled.
Here is the link to performance numbers
https://lore.kernel.org/linux-fsdevel/20220322121212.5087-1-dharamhans87@gmail.com/
Dharmendra Singh (3):
FUSE: Implement atomic lookup + create
Implement atomic lookup + open
Avoid lookup in d_revalidate()
fs/fuse/dir.c | 211 +++++++++++++++++++++++++++++++++++---
fs/fuse/file.c | 30 +++++-
fs/fuse/fuse_i.h | 16 ++-
fs/fuse/inode.c | 4 +-
fs/fuse/ioctl.c | 2 +-
include/uapi/linux/fuse.h | 5 +
6 files changed, 246 insertions(+), 22 deletions(-)
---
v4: Addressed all comments and refactored the code into 3 separate patches
respectively for Atomic create, Atomic open, optimizing lookup in
d_revalidate().
---
next reply other threads:[~2022-05-02 10:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 10:25 Dharmendra Singh [this message]
2022-05-02 10:25 ` [PATCH v4 1/3] FUSE: Implement atomic lookup + create Dharmendra Singh
2022-05-03 12:43 ` Vivek Goyal
2022-05-03 14:13 ` Vivek Goyal
2022-05-03 19:53 ` Vivek Goyal
2022-05-03 20:48 ` Bernd Schubert
2022-05-04 4:26 ` Dharmendra Hans
2022-05-04 14:47 ` Vivek Goyal
2022-05-04 15:46 ` Bernd Schubert
2022-05-04 17:31 ` Vivek Goyal
2022-05-05 4:51 ` Dharmendra Hans
2022-05-05 14:26 ` Vivek Goyal
2022-05-06 5:34 ` Dharmendra Hans
2022-05-06 14:12 ` Vivek Goyal
2022-05-06 16:41 ` Bernd Schubert
2022-05-06 17:07 ` Vivek Goyal
2022-05-06 18:45 ` Bernd Schubert
2022-05-07 10:42 ` Jean-Pierre André
2022-05-07 10:42 ` Jean-Pierre André
2022-05-11 10:08 ` Bernd Schubert
2022-05-02 10:25 ` [PATCH v4 2/3] FUSE: Implement atomic lookup + open Dharmendra Singh
2022-05-04 18:20 ` Vivek Goyal
2022-05-05 6:39 ` Dharmendra Hans
2022-05-02 10:25 ` [PATCH v4 3/3] FUSE: Avoid lookup in d_revalidate() Dharmendra Singh
2022-05-04 20:39 ` Vivek Goyal
2022-05-04 21:05 ` Bernd Schubert
2022-05-05 5:49 ` Dharmendra Hans
2022-05-04 19:18 ` [PATCH v4 0/3] FUSE: Implement atomic lookup + open/create Vivek Goyal
2022-05-05 6:12 ` Dharmendra Hans
2022-05-05 12:54 ` Vivek Goyal
2022-05-05 15:13 ` Bernd Schubert
2022-05-05 19:59 ` Vivek Goyal
2022-05-11 9:40 ` Miklos Szeredi
2022-05-11 9:59 ` Bernd Schubert
2022-05-11 17:21 ` Vivek Goyal
2022-05-11 19:30 ` Vivek Goyal
2022-05-12 8:16 ` Dharmendra Hans
2022-05-12 15:24 ` Vivek Goyal
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=20220502102521.22875-1-dharamhans87@gmail.com \
--to=dharamhans87@gmail.com \
--cc=bschubert@ddn.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.