From: Michal Hocko <mhocko@suse.cz>
To: Glauber Costa <glommer@parallels.com>
Cc: linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
Hugh Dickins <hughd@google.com>, Ying Han <yinghan@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
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: Thu, 20 Oct 2011 09:42:06 -0700 [thread overview]
Message-ID: <20111020164205.GC25505@tiehlicka.suse.cz> (raw)
In-Reply-To: <4E9FE1FC.8080103@parallels.com>
On Thu 20-10-11 12:55:24, Glauber Costa wrote:
> On 10/20/2011 05:33 AM, Michal Hocko wrote:
> >Hi all,
> >this is a request for discussion (I hope we can touch this during memcg
> >meeting during the upcoming KS). I have brought this up earlier this
> >year before LSF (http://thread.gmane.org/gmane.linux.kernel.mm/60464).
> >The patch got much smaller since then due to excellent Johannes' memcg
> >naturalization work (http://thread.gmane.org/gmane.linux.kernel.mm/68724)
> >which this is based on.
> >I realize that this will be controversial but I would like to hear
> >whether this is strictly no-go or whether we can go that direction (the
> >implementation might differ of course).
> >
> >The patch is still half baked but I guess it should be sufficient to
> >show what I am trying to achieve.
> >The basic idea is that memcgs would get a new attribute (isolated) which
> >would control whether that group should be considered during global
> >reclaim.
>
> I'd like to hear a bit more of your use cases,
The primary goal is to isolate the primary workload (e.g. database) from
the rest of the system which provide a support for the primary workload
(backups, administration tools etc). While we can do that even now just
by wrapping everything into different groups and set up proper limits it
gets really tricky if you want to overcommit the box because then the
global reclaim is inevitable so we will start reclaiming from all
groups.
> but at first, I don't like it. I think we should always, regardless of
> any knobs or definitions, be able to globally select a task or set of
> tasks, and kill them.
The patchset is not about OOM but rather about the reclaim. If there is
a global OOM situation we do not care about isolated memcgs.
[...]
--
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>
next prev parent reply other threads:[~2011-10-20 16:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 1:33 [RFD] Isolated memory cgroups again 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 [this message]
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
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=20111020164205.GC25505@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;
as well as URLs for NNTP newsgroup(s).