linux-kernel - Re: [PATCH v5 0/5] Add movablecore

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20130116132953.6159b673.akpm@linux-foundation.org>
Date:	Wed, 16 Jan 2013 13:29:53 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>
Cc:	"Luck, Tony" <tony.luck@...el.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Tang Chen <tangchen@...fujitsu.com>,
	"jiang.liu@...wei.com" <jiang.liu@...wei.com>,
	"wujianguo@...wei.com" <wujianguo@...wei.com>,
	"wency@...fujitsu.com" <wency@...fujitsu.com>,
	"laijs@...fujitsu.com" <laijs@...fujitsu.com>,
	"linfeng@...fujitsu.com" <linfeng@...fujitsu.com>,
	"yinghai@...nel.org" <yinghai@...nel.org>,
	"rob@...dley.net" <rob@...dley.net>,
	"kosaki.motohiro@...fujitsu.com" <kosaki.motohiro@...fujitsu.com>,
	"minchan.kim@...il.com" <minchan.kim@...il.com>,
	"mgorman@...e.de" <mgorman@...e.de>,
	"rientjes@...gle.com" <rientjes@...gle.com>,
	"guz.fnst@...fujitsu.com" <guz.fnst@...fujitsu.com>,
	"rusty@...tcorp.com.au" <rusty@...tcorp.com.au>,
	"lliubbo@...il.com" <lliubbo@...il.com>,
	"jaegeuk.hanse@...il.com" <jaegeuk.hanse@...il.com>,
	"glommer@...allels.com" <glommer@...allels.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [PATCH v5 0/5] Add movablecore_map boot option

On Wed, 16 Jan 2013 15:25:44 +0900
Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com> wrote:

> >
> > Things I'm wondering:
> >
> > - is there *really* a case for retaining the boot option if/when
> >    SRAT support is available?
> 
> Yes. If SRAT support is available, all memory which enabled hotpluggable
> bit are managed by ZONEMOVABLE. But performance degradation may
> occur by NUMA because we can only allocate anonymous page and page-cache
> from these memory.
> 
> In this case, if user cannot change SRAT information, user needs a way to
> select/set removable memory manually.

If I understand this correctly you mean that once SRAT parsing is
implemented, the user can use movablecore_map to override that SRAT
parsing, yes?  That movablecore_map will take precedence over SRAT?

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