On Fri, 2020-06-05 at 10:23 +0200, Igor Mammedov wrote:
> > > > The relevant command line options to exercise this are below. Nodes 0-1
> > > > contain CPUs and regular memory, and nodes 2-3 are the NVDIMM address
> > > > space.
> > > >
> > > > -numa node,nodeid=0,mem=2048M,
> > > > -numa nod
On Fri, 5 Jun 2020 00:54:28 +
"Verma, Vishal L" wrote:
> On Thu, 2020-06-04 at 12:33 +0200, Igor Mammedov wrote:
> > On Thu, 28 May 2020 16:34:36 -0600
> > Vishal Verma wrote:
> >
> > > NVDIMMs can belong to their own proximity domains, as described by the
> > > NFIT. In such cases, the S
On Thu, 2020-06-04 at 12:33 +0200, Igor Mammedov wrote:
> On Thu, 28 May 2020 16:34:36 -0600
> Vishal Verma wrote:
>
> > NVDIMMs can belong to their own proximity domains, as described by the
> > NFIT. In such cases, the SRAT needs to have Memory Affinity structures
> > in the SRAT for these NVDI
On Thu, 28 May 2020 16:34:36 -0600
Vishal Verma wrote:
> NVDIMMs can belong to their own proximity domains, as described by the
> NFIT. In such cases, the SRAT needs to have Memory Affinity structures
> in the SRAT for these NVDIMMs, otherwise Linux doesn't populate node
> data structures properl
NVDIMMs can belong to their own proximity domains, as described by the
NFIT. In such cases, the SRAT needs to have Memory Affinity structures
in the SRAT for these NVDIMMs, otherwise Linux doesn't populate node
data structures properly during NUMA initialization. See the following
for an example fa
