From: Michal Hocko <mhocko@suse.cz>
To: Balbir Singh <bsingharora@gmail.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
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>, Ying Han <yinghan@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:26:16 +0200 [thread overview]
Message-ID: <20111022092524.GA5497@tiehlicka.suse.cz> (raw)
In-Reply-To: <CAKTCnz=iZp37sBfY++HUU0oscskFF_UWYeFYtAujtQh4_B=vHQ@mail.gmail.com>
On Fri 21-10-11 21:34:06, Balbir Singh wrote:
> On Thu, Oct 20, 2011 at 7:29 AM, KAMEZAWA Hiroyuki
> <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> > On Wed, 19 Oct 2011 18:33:09 -0700
> > Michal Hocko <mhocko@suse.cz> 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.
> >
>
> Hi, Michal
Hi Balbir,
>
> I'd like to understand, what the isolation is for?
>
> 1. Is it an alternative to memory guarantees?
Not really, it is more about resident working set guarantee and workload
isolations wrt. memory.
> 2. How is this different from doing cpusets (fake NUMA) and isolating them?
Yes this would work. I have not many experiences in this area but I
guess the primary stopper for fake NUMA is that it is x86_64 only,
configuration is static and little bit awkward to use (nodes of the same
size e.g.).
I understood that google is moving out of fake NUMA towards memcg for those
reasons.
>
> Just trying to catch up,
> Balbir
--
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-22 9:26 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 [this message]
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
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=20111022092524.GA5497@tiehlicka.suse.cz \
--to=mhocko@suse.cz \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--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).