From: Matthew Wilcox <willy@infradead.org>
To: Roman Gushchin <roman.gushchin@linux.dev>
Cc: Stephen Brennan <stephen.s.brennan@oracle.com>,
lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org,
Gautham Ananthakrishna <gautham.ananthakrishna@oracle.com>,
khlebnikov@yandex-team.ru
Subject: Re: [LSF/MM TOPIC] Better handling of negative dentries
Date: Tue, 22 Mar 2022 20:41:56 +0000 [thread overview]
Message-ID: <Yjo0lA3DiX1fFTue@casper.infradead.org> (raw)
In-Reply-To: <A35C545C-1926-4AA9-BFC7-0CF11669EA9E@linux.dev>
On Tue, Mar 15, 2022 at 01:56:18PM -0700, Roman Gushchin wrote:
> I’d be happy to join this discussion. And in my opinion it’s going
> beyond negative dentries: there are other types of objects which tend
> to grow beyond any reasonable limits if there is no memory pressure.
>
> A perfect example when it happens is when a machine is almost idle
> for some period of time. Periodically running processes creating
> various kernel objects (mostly vfs cache) which over time are filling
> significant portions of the total memory. And when the need for memory
> arises, we realize that the memory is heavily fragmented and it’s
> costly to reclaim it back.
When you say "vfs cache", do you mean page cache, inode cache, or
something else?
next prev parent reply other threads:[~2022-03-22 20:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 19:55 [LSF/MM TOPIC] Better handling of negative dentries Matthew Wilcox
2022-03-15 20:56 ` Roman Gushchin
2022-03-16 2:07 ` Gao Xiang
2022-03-16 2:52 ` Dave Chinner
2022-03-16 3:08 ` Gao Xiang
2022-03-22 15:08 ` Matthew Wilcox
2022-03-22 19:19 ` James Bottomley
2022-03-22 20:17 ` Colin Walters
2022-03-22 20:27 ` James Bottomley
2022-03-22 20:37 ` Matthew Wilcox
2022-03-22 21:08 ` Stephen Brennan
2022-03-29 15:24 ` James Bottomley
2022-03-31 19:27 ` Stephen Brennan
2022-04-01 15:45 ` James Bottomley
2022-03-22 22:21 ` Dave Chinner
2022-03-22 20:41 ` Matthew Wilcox [this message]
2022-03-22 21:19 ` Roman Gushchin
2022-03-22 22:29 ` Dave Chinner
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=Yjo0lA3DiX1fFTue@casper.infradead.org \
--to=willy@infradead.org \
--cc=gautham.ananthakrishna@oracle.com \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=roman.gushchin@linux.dev \
--cc=stephen.s.brennan@oracle.com \
/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).