From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Cc: [email protected], [email protected]
Subject: [PATCHSET RFC] support RESOLVE_CACHED for statx
Date: Mon, 25 Jan 2021 14:36:11 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
This is a followup to the RESOLVE_CACHED addition that allows us to
speedup the io_uring open side (and enable RESOLVE_CACHED through
openat2). Mostly straight forward, as you can see from patch 1, this
just adds AT_STATX_CACHED that sits on top of that. Patch 2 is the
mostly ugly part, but not sure how we can do this any better - we need
to ensure that any sort of revalidation or sync in ->getattr() honors
it too. Patch 3 is just adapting to this in io_uring.
fs/9p/vfs_inode.c | 2 ++
fs/afs/inode.c | 3 +++
fs/ceph/inode.c | 2 ++
fs/cifs/inode.c | 3 +++
fs/coda/inode.c | 7 ++++++-
fs/ecryptfs/inode.c | 3 +++
fs/fuse/dir.c | 2 ++
fs/gfs2/inode.c | 2 ++
fs/io_uring.c | 21 ++++++++++++++-------
fs/kernfs/inode.c | 8 +++++++-
fs/nfs/inode.c | 3 +++
fs/ocfs2/file.c | 3 +++
fs/orangefs/inode.c | 3 +++
fs/stat.c | 4 +++-
fs/ubifs/dir.c | 7 ++++++-
fs/udf/symlink.c | 3 +++
fs/vboxsf/utils.c | 4 ++++
include/uapi/linux/fcntl.h | 2 ++
18 files changed, 71 insertions(+), 11 deletions(-)
--
Jens Axboe
next reply other threads:[~2021-01-25 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 21:36 Jens Axboe [this message]
2021-01-25 21:36 ` [PATCH 1/3] fs: add support for AT_STATX_CACHED Jens Axboe
2021-01-25 21:36 ` [PATCH 2/3] fs: ensure that ->getattr() honors AT_STATX_CACHED Jens Axboe
2021-01-25 21:36 ` [PATCH 3/3] io_uring: use AT_STATX_CACHED for IORING_OP_STATX fast path Jens Axboe
2021-01-25 23:39 ` [PATCHSET RFC] support RESOLVE_CACHED for statx Linus Torvalds
2021-01-26 1:06 ` Jens Axboe
2021-01-26 1:28 ` Linus Torvalds
2021-01-26 1:31 ` Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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