linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: Ying Han <yinghan@google.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
	Hugh Dickins <hughd@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Glauber Costa <glommer@parallels.com>,
	Kir Kolyshkin <kir@parallels.com>,
	Pavel Emelianov <xemul@parallels.com>,
	GregThelen <gthelen@google.com>,
	"pjt@google.com" <pjt@google.com>,
	Tim Hockin <thockin@google.com>,
	Dave Hansen <dave@linux.vnet.ibm.com>,
	Paul Menage <paul@paulmenage.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [RFD] Isolated memory cgroups again
Date: Sat, 22 Oct 2011 11:31:48 +0200	[thread overview]
Message-ID: <20111022093148.GB5497@tiehlicka.suse.cz> (raw)
In-Reply-To: <CALWz4iw9OGUNKjD5y2xGDGaesTjwUT5TOL2A7wDd5apy4M5fnw@mail.gmail.com>

On Fri 21-10-11 13:00:18, Ying Han wrote:
[...]
> The logic is based on reclaim priority, and we skip reclaim from certain
> memcg(under soft limit) before getting down to DEF_PRIORITY - 3.

OK, I guess I remember something from the earlier memcg naturalization
patch set discussions. This will still not help much for my case as the
bigger memory pressure would cause reclaim also from the soft unlimited
group which I would like to prevent.
The other thing about soft limit only reclaim from the global reclaim is
that currently all created memcgs are soft unlimited by default which
might lead to unexpected results. Can we come up with a reasonable soft
limit default?

[...]
-- 
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-10-22  9:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-20  1:33 Michal Hocko
2011-10-20  1:59 ` KAMEZAWA Hiroyuki
2011-10-20 16:30   ` Michal Hocko
2011-10-21 16:04   ` Balbir Singh
2011-10-22  9:26     ` Michal Hocko
2011-10-21 16:11   ` Balbir Singh
2011-10-20  8:55 ` Glauber Costa
2011-10-20 16:42   ` Michal Hocko
2011-10-20 23:41 ` Ying Han
2011-10-21  2:45   ` Michal Hocko
2011-10-21  3:17     ` KAMEZAWA Hiroyuki
2011-10-21 20:00       ` Ying Han
2011-10-22  9:31         ` Michal Hocko [this message]
2011-10-21  8:39   ` Glauber Costa
2011-10-21 12:16     ` Johannes Weiner
2011-10-22  9:47     ` Michal Hocko

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=20111022093148.GB5497@tiehlicka.suse.cz \
    --to=mhocko@suse.cz \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=glommer@parallels.com \
    --cc=gthelen@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kir@parallels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nishimura@mxp.nes.nec.co.jp \
    --cc=paul@paulmenage.org \
    --cc=pjt@google.com \
    --cc=thockin@google.com \
    --cc=xemul@parallels.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