From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Unnecessarily bad cache behavior for ext4_getattr()
Date: Sun, 24 Nov 2019 16:19:16 -0800 [thread overview]
Message-ID: <CAHk-=wivmk_j6KbTX+Er64mLrG8abXZo0M10PNdAnHc8fWXfsQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
It looks from profiles like ext4_getattr() is fairly expensive,
because it unnecessarily accesses the extended inode information and
causes extra cache misses.
On an empty kernel allmodconfig build (which is a lot of "stat()"
calls by Make, and a lot of silly string stuff in user space due to
all the make variable games we play), ext4_getattr() was something
like 1% of the time according to the profile I gathered. It might be
bogus - maybe the cacheline ends up being accessed later anyway, but
it _looked_ like it was the whole "i_extra_isize" access that missed
in the cache.
That's all for gathering the STATX_BTIME information, that the caller
doesn't even *want*.
How about a patch like the attached?
Linus
[-- Attachment #2: patch.diff --]
[-- Type: text/x-patch, Size: 623 bytes --]
fs/ext4/inode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
index 516faa280ced..617dc8835f5f 100644
--- a/fs/ext4/inode.c
+++ b/fs/ext4/inode.c
@@ -5700,7 +5700,7 @@ int ext4_getattr(const struct path *path, struct kstat *stat,
struct ext4_inode_info *ei = EXT4_I(inode);
unsigned int flags;
- if (EXT4_FITS_IN_INODE(raw_inode, ei, i_crtime)) {
+ if ((query_flags & STATX_BTIME) && EXT4_FITS_IN_INODE(raw_inode, ei, i_crtime)) {
stat->result_mask |= STATX_BTIME;
stat->btime.tv_sec = ei->i_crtime.tv_sec;
stat->btime.tv_nsec = ei->i_crtime.tv_nsec;
next reply other threads:[~2019-11-25 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 0:19 Linus Torvalds [this message]
2019-11-25 20:35 ` Unnecessarily bad cache behavior for ext4_getattr() Andreas Dilger
2019-11-30 0:49 ` Theodore Y. Ts'o
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='CAHk-=wivmk_j6KbTX+Er64mLrG8abXZo0M10PNdAnHc8fWXfsQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).