From: Matthew Wilcox <willy@infradead.org>
To: Daniel Drake <drake@endlessm.com>
Cc: mhocko@kernel.org, hannes@cmpxchg.org, linux-mm@kvack.org,
linux@endlessm.com, linux-kernel@vger.kernel.org
Subject: Re: Making direct reclaim fail when thrashing
Date: Fri, 27 Jul 2018 12:01:22 -0700 [thread overview]
Message-ID: <20180727190122.GA3825@bombadil.infradead.org> (raw)
In-Reply-To: <20180727162143.26466-1-drake@endlessm.com>
On Fri, Jul 27, 2018 at 11:21:43AM -0500, Daniel Drake wrote:
> Here I'm experimenting by adding another tag to the page cache radix tree,
> tagging pages that were activated in the refault path.
NAK. No more tags or you blow up the memory consumption of the radix
tree by 15%.
> And then in get_scan_count I'm checking how many active pages have that
> tag, and also looking at the size of the active and inactive lists.
You'd be better off using a bit in struct page somewhere ...
next prev parent reply other threads:[~2018-07-27 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 16:21 Making direct reclaim fail when thrashing Daniel Drake
2018-07-27 19:01 ` Matthew Wilcox [this message]
2018-07-27 20:22 ` Johannes Weiner
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=20180727190122.GA3825@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=drake@endlessm.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@endlessm.com \
--cc=mhocko@kernel.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;
as well as URLs for NNTP newsgroup(s).