From: Linus Torvalds <torvalds@linux-foundation.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Waiman Long <longman@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Jan Kara <jack@suse.cz>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@kernel.org>,
Miklos Szeredi <mszeredi@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
Larry Woodman <lwoodman@redhat.com>,
"Wangkai (Kevin,C)" <wangkai86@huawei.com>,
linux-mm <linux-mm@kvack.org>, Michal Hocko <mhocko@kernel.org>
Subject: Re: [PATCH v5 0/6] fs/dcache: Track & limit # of negative dentries
Date: Mon, 2 Jul 2018 15:54:04 -0700 [thread overview]
Message-ID: <CA+55aFzyUb07Lt251bzi4T79oB=M8uypFQ2m__FgnRJUauqd0Q@mail.gmail.com> (raw)
In-Reply-To: <1530570880.3179.9.camel@HansenPartnership.com>
On Mon, Jul 2, 2018 at 3:34 PM James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
>
> There are still a lot of applications that keep looking up non-existent
> files, so I think it's still beneficial to keep them. Apparently
> apache still looks for a .htaccess file in every directory it
> traverses, for instance.
.. or git looking for ".gitignore" files in every directory, or any
number of similar things.
Lookie here, for example:
[torvalds@i7 linux]$ strace -e trace=%file -c git status
On branch master
Your branch is up to date with 'origin/master'.
nothing to commit, working tree clean
% time seconds usecs/call calls errors syscall
------ ----------- ----------- --------- --------- ----------------
73.23 0.009066 2 4056 6 open
23.33 0.002888 2 1294 1189 openat
1.60 0.000198 13 15 8 access
0.80 0.000099 2 36 31 lstat
0.53 0.000066 1 40 6 stat
0.27 0.000033 8 4 getcwd
0.11 0.000014 14 1 execve
0.11 0.000014 14 1 chdir
0.02 0.000003 3 1 1 readlink
0.00 0.000000 0 1 unlink
------ ----------- ----------- --------- --------- ----------------
100.00 0.012381 5449 1241 total
so almost a quarter (1241 of 5449) of the file accesses resulted in
errors (and I think they are all ENOENT).
Negative lookups are *not* some unusual thing.
Linus
next prev parent reply other threads:[~2018-07-02 22:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1530510723-24814-1-git-send-email-longman@redhat.com>
[not found] ` <CA+55aFyH6dHw-7R3364dn32J4p7kxT=TqmnuozCn9_Bz-MHhxQ@mail.gmail.com>
2018-07-02 21:18 ` Andrew Morton
2018-07-02 22:21 ` Matthew Wilcox
2018-07-02 22:31 ` Linus Torvalds
2018-07-02 22:34 ` James Bottomley
2018-07-02 22:54 ` Linus Torvalds [this message]
2018-07-02 23:03 ` Linus Torvalds
2018-07-02 23:19 ` Andrew Morton
2018-07-02 23:28 ` Linus Torvalds
2018-07-03 1:38 ` Waiman Long
2018-07-03 9:18 ` Jan Kara
2018-07-14 17:35 ` Pavel Machek
2018-07-14 18:00 ` Linus Torvalds
2018-07-14 18:34 ` Al Viro
2018-07-14 18:36 ` Al Viro
2018-07-14 18:43 ` Linus Torvalds
2018-07-18 16:01 ` Waiman Long
2018-07-03 1:11 ` Waiman Long
2018-07-03 13:48 ` Vlastimil Babka
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='CA+55aFzyUb07Lt251bzi4T79oB=M8uypFQ2m__FgnRJUauqd0Q@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=lwoodman@redhat.com \
--cc=mhocko@kernel.org \
--cc=mingo@kernel.org \
--cc=mszeredi@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wangkai86@huawei.com \
--cc=willy@infradead.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