From: Rik van Riel <riel@redhat.com>
To: Dave Chinner <dchinner@redhat.com>
Cc: Glauber Costa <glommer@parallels.com>,
Ying Han <yinghan@google.com>, Michal Hocko <mhocko@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>, Mel Gorman <mel@csn.ul.ie>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Greg Thelen <gthelen@google.com>,
Christoph Lameter <cl@linux.com>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
linux-mm@kvack.org
Subject: Re: [RFC PATCH 0/6] memcg: vfs isolation in memory cgroup
Date: Fri, 17 Aug 2012 10:44:47 -0400 [thread overview]
Message-ID: <502E58DF.4000809@redhat.com> (raw)
In-Reply-To: <20120817075440.GD2776@devil.redhat.com>
On 08/17/2012 03:54 AM, Dave Chinner wrote:
> IOWs, it's still the same count/scan shrinker interface, just with
> all the LRU and shrinker bits abstracted and implemented in common
> code. The generic LRU abstraction is that it only knows about the
> list-head in the structure that is passed to it, and it passes that
> listhead to the per-object callbacks for the subsystem to do the
> specific work that is needed.
This will make it very easy to iterate over the slab object
LRUs in my "reclaim from the highest score LRU" patch set.
That in turn will allow us to properly balance pressure between
cgroup and non-cgroup object LRUs, between the LRUs of various
superblocks, etc...
--
All rights reversed
--
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:[~2012-08-17 14:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 20:53 [RFC PATCH 0/6] memcg: vfs isolation in memory cgroup Ying Han
2012-08-16 21:10 ` Rik van Riel
2012-08-16 23:41 ` Dave Chinner
2012-08-17 5:15 ` Glauber Costa
2012-08-17 5:40 ` Ying Han
2012-08-17 5:42 ` Glauber Costa
2012-08-17 7:56 ` Dave Chinner
2012-08-19 3:41 ` Andi Kleen
2012-08-17 7:54 ` Dave Chinner
2012-08-17 10:00 ` Glauber Costa
2012-08-17 19:18 ` Ying Han
2012-08-17 14:44 ` Rik van Riel [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=502E58DF.4000809@redhat.com \
--to=riel@redhat.com \
--cc=cl@linux.com \
--cc=dchinner@redhat.com \
--cc=glommer@parallels.com \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mhocko@suse.cz \
--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).