[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <01000167f14761d6-b1564081-0d5f-4752-86be-2e99c8375866-000000@email.amazonses.com>
Date: Thu, 27 Dec 2018 20:07:26 +0000
From: Christopher Lameter <cl@...ux.com>
To: Fengguang Wu <fengguang.wu@...el.com>
cc: Andrew Morton <akpm@...ux-foundation.org>,
Linux Memory Management List <linux-mm@...ck.org>,
Fan Du <fan.du@...el.com>, kvm@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Yao Yuan <yuan.yao@...el.com>,
Peng Dong <dongx.peng@...el.com>,
Huang Ying <ying.huang@...el.com>,
Liu Jingqi <jingqi.liu@...el.com>,
Dong Eddie <eddie.dong@...el.com>,
Dave Hansen <dave.hansen@...el.com>,
Zhang Yi <yi.z.zhang@...ux.intel.com>,
Dan Williams <dan.j.williams@...el.com>
Subject: Re: [RFC][PATCH v2 08/21] mm: introduce and export pgdat peer_node
On Wed, 26 Dec 2018, Fengguang Wu wrote:
> Each CPU socket can have 1 DRAM and 1 PMEM node, we call them "peer nodes".
> Migration between DRAM and PMEM will by default happen between peer nodes.
Which one does numa_node_id() point to? I guess that is the DRAM node and
then we fall back to the PMEM node?
Powered by blists - more mailing lists