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
| ||
|
Date: Thu, 15 Nov 2012 16:29:20 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: Wen Congyang <wency@...fujitsu.com> Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org, linux-doc@...r.kernel.org, Rob Landley <rob@...dley.net>, Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>, Lai Jiangshan <laijs@...fujitsu.com>, Jiang Liu <jiang.liu@...wei.com>, KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>, Minchan Kim <minchan.kim@...il.com>, Mel Gorman <mgorman@...e.de>, David Rientjes <rientjes@...gle.com>, Yinghai Lu <yinghai@...nel.org>, Rusty Russell <rusty@...tcorp.com.au>, Lin feng <linfeng@...fujitsu.com> Subject: Re: [PART3 Patch v2 13/14] page_alloc: use N_MEMORY instead N_HIGH_MEMORY change the node_states initialization On Thu, 15 Nov 2012 16:57:36 +0800 Wen Congyang <wency@...fujitsu.com> wrote: > N_HIGH_MEMORY stands for the nodes that has normal or high memory. > N_MEMORY stands for the nodes that has any memory. > > The code here need to handle with the nodes which have memory, we should > use N_MEMORY instead. > > Since we introduced N_MEMORY, we update the initialization of node_states. reset_zone_present_pages() has been removed by the recently-queued revert-mm-fix-up-zone-present-pages.patch, so I dropped that hunk. We still have akpm:/usr/src/25> grep N_HIGH_MEMORY mm/page_alloc.c [N_HIGH_MEMORY] = { { [0] = 1UL } }, node_set_state(nid, N_HIGH_MEMORY); if (N_NORMAL_MEMORY != N_HIGH_MEMORY && which I hope is correct. Can you please check it? -- 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