From: Rik van Riel <riel@redhat.com>
To: Ying Han <yinghan@google.com>
Cc: 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>,
Glauber Costa <glommer@parallels.com>,
linux-mm@kvack.org, dchinner@redhat.com
Subject: Re: [RFC PATCH 0/6] memcg: vfs isolation in memory cgroup
Date: Thu, 16 Aug 2012 17:10:57 -0400 [thread overview]
Message-ID: <502D61E1.8040704@redhat.com> (raw)
In-Reply-To: <1345150417-30856-1-git-send-email-yinghan@google.com>
On 08/16/2012 04:53 PM, Ying Han wrote:
> The patchset adds the functionality of isolating the vfs slab objects per-memcg
> under reclaim. This feature is a *must-have* after the kernel slab memory
> accounting which starts charging the slab objects into individual memcgs. The
> existing per-superblock shrinker doesn't work since it will end up reclaiming
> slabs being charged to other memcgs.
> The patch now is only handling dentry cache by given the nature dentry pinned
> inode. Based on the data we've collected, that contributes the main factor of
> the reclaimable slab objects. We also could make a generic infrastructure for
> all the shrinkers (if needed).
Dave Chinner has some prototype code for that.
As an aside, the slab LRUs can also keep
recent_scanned, recent_rotated and recent_pressure
statistics, so we can balance pressure between the
normal page LRUs and the slab LRUs in the exact
same way my patch series balances pressure between
cgroups.
This could be important, because the slab LRUs
span multiple memory zones, while the normal page
LRUs only live in one memory zone each.
--
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>
next prev parent reply other threads:[~2012-08-16 21:13 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 [this message]
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
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=502D61E1.8040704@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).