lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 22 Oct 2011 11:26:16 +0200
From:	Michal Hocko <mhocko@...e.cz>
To:	Balbir Singh <bsingharora@...il.com>
Cc:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	linux-mm@...ck.org, LKML <linux-kernel@...r.kernel.org>,
	Johannes Weiner <hannes@...xchg.org>,
	Daisuke Nishimura <nishimura@....nes.nec.co.jp>,
	Hugh Dickins <hughd@...gle.com>, Ying Han <yinghan@...gle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Glauber Costa <glommer@...allels.com>,
	Kir Kolyshkin <kir@...allels.com>,
	Pavel Emelianov <xemul@...allels.com>,
	GregThelen <gthelen@...gle.com>,
	"pjt@...gle.com" <pjt@...gle.com>, Tim Hockin <thockin@...gle.com>,
	Dave Hansen <dave@...ux.vnet.ibm.com>,
	Paul Menage <paul@...lmenage.org>,
	James Bottomley <James.Bottomley@...senpartnership.com>
Subject: Re: [RFD] Isolated memory cgroups again

On Fri 21-10-11 21:34:06, Balbir Singh wrote:
> On Thu, Oct 20, 2011 at 7:29 AM, KAMEZAWA Hiroyuki
> <kamezawa.hiroyu@...fujitsu.com> wrote:
> > On Wed, 19 Oct 2011 18:33:09 -0700
> > Michal Hocko <mhocko@...e.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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ