From: Matthew Wilcox <willy@infradead.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Andreas Dilger <adilger@dilger.ca>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
Amir Goldstein <amir73il@gmail.com>, Jan Kara <jack@suse.cz>,
Ian Kent <raven@themaw.net>
Subject: Re: bad things when too many negative dentries in a directory
Date: Wed, 16 Apr 2025 16:37:04 +0100 [thread overview]
Message-ID: <Z__OoG1cE_f7Z64_@casper.infradead.org> (raw)
In-Reply-To: <CAJfpegtchAYvz8vLzrAkVy5WmV-Zc1PLbXUuwzxpiBCPOhK5Rg@mail.gmail.com>
On Wed, Apr 16, 2025 at 05:18:17PM +0200, Miklos Szeredi wrote:
> Lack of memory pressure should mean that nobody else needs that
> memory, so it should make no difference if it's used up in negative
> dentries instead of being free memory. Maybe I'm missing something
> fundamental?
You're missing two things:
- The dentry hash table is a fixed size. Long chains give poor
performance, so polluting the hash table with unused entries
has a cost.
- Eventually, we do trigger reclaim. And then we wait for hours while
the reclaiming process tries to shrink billions of entries. I think
we had a report on one machine of it taking more than 24 hours ("more
than" because the customer decided enough was enough and rebooted the
machine).
next prev parent reply other threads:[~2025-04-16 15:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 9:40 bad things when too many negative dentries in a directory Miklos Szeredi
2025-04-11 14:47 ` Christian Brauner
2025-04-11 15:40 ` Miklos Szeredi
2025-04-11 16:01 ` Matthew Wilcox
2025-04-14 14:07 ` James Bottomley
2025-04-14 14:30 ` Matthew Wilcox
2025-04-14 15:40 ` James Bottomley
2025-04-14 16:14 ` Matthew Wilcox
2025-04-14 17:58 ` James Bottomley
2025-04-15 17:22 ` Andreas Dilger
2025-04-16 15:18 ` Miklos Szeredi
2025-04-16 15:37 ` Matthew Wilcox [this message]
2025-04-16 21:41 ` Dave Chinner
2025-04-16 15:26 ` James Bottomley
2025-04-22 6:57 ` Andreas Dilger
2025-04-14 6:28 ` Ian Kent
2025-04-14 7:17 ` Miklos Szeredi
2025-04-12 1:48 ` Ian Kent
2025-04-12 1:56 ` Ian Kent
2025-04-12 6:31 ` Ian Kent
2025-04-11 21:02 ` Mateusz Guzik
2025-04-20 4:49 ` Al Viro
2025-05-08 15:45 ` Miklos Szeredi
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=Z__OoG1cE_f7Z64_@casper.infradead.org \
--to=willy@infradead.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=adilger@dilger.ca \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=raven@themaw.net \
--cc=viro@zeniv.linux.org.uk \
/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