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: Wed, 12 Jan 2022 17:10:23 +0100 From: Peter Zijlstra <peterz@...radead.org> To: Huang Ying <ying.huang@...el.com> Cc: Mel Gorman <mgorman@...e.de>, linux-mm@...ck.org, linux-kernel@...r.kernel.org, Feng Tang <feng.tang@...el.com>, Andrew Morton <akpm@...ux-foundation.org>, Michal Hocko <mhocko@...e.com>, Rik van Riel <riel@...riel.com>, Mel Gorman <mgorman@...hsingularity.net>, Dave Hansen <dave.hansen@...ux.intel.com>, Yang Shi <shy828301@...il.com>, Zi Yan <ziy@...dia.com>, Wei Xu <weixugc@...gle.com>, osalvador <osalvador@...e.de>, Shakeel Butt <shakeelb@...gle.com>, Hasan Al Maruf <hasanalmaruf@...com> Subject: Re: [PATCH -V10 RESEND 0/6] NUMA balancing: optimize memory placement for memory tiering system On Tue, Dec 07, 2021 at 10:27:51AM +0800, Huang Ying wrote: > After commit c221c0b0308f ("device-dax: "Hotplug" persistent memory > for use like normal RAM"), the PMEM could be used as the > cost-effective volatile memory in separate NUMA nodes. In a typical > memory tiering system, there are CPUs, DRAM and PMEM in each physical > NUMA node. The CPUs and the DRAM will be put in one logical node, > while the PMEM will be put in another (faked) logical node. So what does a system like that actually look like, SLIT table wise, and how does that affect init_numa_topology_type() ?
Powered by blists - more mailing lists