From: Johannes Weiner <hannes@cmpxchg.org>
To: Rik van Riel <riel@redhat.com>
Cc: Andres Freund <andres@anarazel.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: Unhelpful caching decisions, possibly related to active/inactive sizing
Date: Fri, 12 Feb 2016 15:24:05 -0500 [thread overview]
Message-ID: <20160212202405.GA32367@cmpxchg.org> (raw)
In-Reply-To: <20160211153404.42055b27@cuia.usersys.redhat.com>
On Thu, Feb 11, 2016 at 03:34:04PM -0500, Rik van Riel wrote:
> On Tue, 9 Feb 2016 17:42:56 -0500
> Johannes Weiner <hannes@cmpxchg.org> wrote:
> > On Tue, Feb 09, 2016 at 05:52:40PM +0100, Andres Freund wrote:
>
> > > Rik asked me about active/inactive sizing in /proc/meminfo:
> > > Active: 7860556 kB
> > > Inactive: 5395644 kB
> > > Active(anon): 2874936 kB
> > > Inactive(anon): 432308 kB
> > > Active(file): 4985620 kB
> > > Inactive(file): 4963336 kB
>
> > Yes, a generous minimum size of the inactive list made sense when it
> > was the exclusive staging area to tell use-once pages from use-many
> > pages. Now that we have refault information to detect use-many with
> > arbitrary inactive list size, this minimum is no longer reasonable.
> >
> > The new minimum should be smaller, but big enough for applications to
> > actually use the data in their pages between fault and eviction
> > (i.e. it needs to take the aggregate readahead window into account),
> > and big enough for active pages that are speculatively challenged
> > during workingset changes to get re-activated without incurring IO.
> >
> > However, I don't think it makes sense to dynamically adjust the
> > balance between the active and the inactive cache during refaults.
>
> Johannes, does this patch look ok to you?
Yes, the anon ratio we use looks like a good fit for file as well.
I've updated the patch to work with cgroups.
next prev parent reply other threads:[~2016-02-12 20:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 16:52 Unhelpful caching decisions, possibly related to active/inactive sizing Andres Freund
2016-02-09 22:42 ` Johannes Weiner
2016-02-11 20:34 ` Rik van Riel
2016-02-12 12:46 ` Andres Freund
2016-02-12 19:35 ` Andres Freund
2016-02-16 19:29 ` Johannes Weiner
2016-02-17 21:17 ` Rik van Riel
2016-02-19 22:19 ` Andres Freund
2016-02-12 12:56 ` Andres Freund
2016-02-12 20:24 ` Johannes Weiner [this message]
2016-02-19 22:07 ` Andres Freund
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=20160212202405.GA32367@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=andres@anarazel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=vbabka@suse.cz \
/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).