[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC PATCH 6/8] nvdimm: add PPC64 'device-node' property

From: Daniel Henrique Barboza
Subject: Re: [RFC PATCH 6/8] nvdimm: add PPC64 'device-node' property
Date: Tue, 15 Jun 2021 17:13:31 -0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1

On 6/15/21 6:33 AM, Aneesh Kumar K.V wrote:
Daniel Henrique Barboza <danielhb413@gmail.com> writes:

The spapr-nvdimm driver is able to operate in two ways. The first
one is as a regular memory in which the NUMA node of the parent
pc-dimm class is used. The second mode, as persistent memory, allows for
a different NUMA node to be used based on the locality of the device.

At this moment we don't have a way to express this second NUMA node for
the persistent memory mode. This patch introduces a new 'device-node'
property that will be used by the PPC64 spapr-nvdimm driver to set a
second NUMA node for the nvdimm.

if device-node is not specified on the commandline, we should default to
the same value of node= attribute? Right now I am finding this default
to 0.

I agree. I fixed it in the next version to default to the 'node'
value when 'device-node' is omitted.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]