From: Andrew Morton <akpm@linux-foundation.org>
To: Ying Han <yinghan@google.com>
Cc: linux-mm@kvack.org, Alexander Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@lst.de>, Nick Piggin <npiggin@suse.de>,
Paul Turner <pjt@google.com>, Mel Gorman <mel@csn.ul.ie>
Subject: Re: [PATCH] Fix ext2 and ext4 buffer-head accounting.
Date: Fri, 29 Oct 2010 16:19:11 -0700 [thread overview]
Message-ID: <20101029161911.046abe8a.akpm@linux-foundation.org> (raw)
In-Reply-To: <1288199797-22541-1-git-send-email-yinghan@google.com>
On Wed, 27 Oct 2010 10:16:37 -0700
Ying Han <yinghan@google.com> wrote:
> Pages pinned to block group_descriptors in the super_block are non-reclaimable.
> Those pages are showed up as file-backed in meminfo which confuse user program
> issuing too many drop_caches/ttfp when this memory will never be freed.
>
> The change has us not account for the file system descriptors by taking the pages
> off LRU and decrementing the NR_FILE_PAGES counter. The pages are putting back when
> the filesystem is being unmounted.
Well, it's not just ext2 and ext4.
Is this the simplest way of solving the problem? This is just pinned
pagecache. We already have way of handling pinned pagecache (eg,
mlocked pages). Can we reuse those mechanisms, perhaps after suitable
generalisation?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2010-10-29 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 17:16 [PATCH] Fix ext2 and ext4 buffer-head accounting Ying Han
2010-10-29 23:19 ` Andrew Morton [this message]
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=20101029161911.046abe8a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=npiggin@suse.de \
--cc=pjt@google.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yinghan@google.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).