linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <dchinner@redhat.com>
To: Glauber Costa <glommer@parallels.com>
Cc: Ying Han <yinghan@google.com>, Rik van Riel <riel@redhat.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 17:56:13 +1000	[thread overview]
Message-ID: <20120817075613.GE2776@devil.redhat.com> (raw)
In-Reply-To: <502DD9B7.5070604@parallels.com>

On Fri, Aug 17, 2012 at 09:42:15AM +0400, Glauber Costa wrote:
> On 08/17/2012 09:40 AM, Ying Han wrote:
> >> > 2) There is no memcg associated with the object, and then we should not
> >> > bother with that object at all.
> > In the patch I have, all objects are associated with *a* memcg. For
> > those objects are charged to root or reparented to root,
> > they do get associated with root and further memory pressure on root (
> > global reclaim ) will be applied on those objects.
> > 
> For the practical purposes of what Dave is concerned about, "no memcg"
> equals "root memcg", right? It still holds we would expect globally
> accessed dentries to belong to root/no-memcg, and per-group pressure
> would not get to them.

Exactly.

Cheers,

Dave.
-- 
Dave Chinner
dchinner@redhat.com

--
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>

  reply	other threads:[~2012-08-17  7:56 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 [this message]
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=20120817075613.GE2776@devil.redhat.com \
    --to=dchinner@redhat.com \
    --cc=cl@linux.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=riel@redhat.com \
    --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).