[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <30db4768-5dc8-d493-1bac-03f382e867e4@inria.fr>
Date: Wed, 10 Apr 2019 13:07:37 +0200
From: Brice Goglin <Brice.Goglin@...ia.fr>
To: Keith Busch <keith.busch@...el.com>, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org, linux-mm@...ck.org
Cc: Rafael Wysocki <rafael@...nel.org>,
Dave Hansen <dave.hansen@...el.com>,
Dan Williams <dan.j.williams@...el.com>
Subject: Re: [PATCH] hmat: Register attributes for memory hot add
Thanks Keith, this solves my issue.
On a machine where node4 (PMEM) is close to node0 and node1 (1st socket
SNCs), hotplugging that node makes node0 and node1 appear as initiators
to node4 (and node4 as target to them). Same for the other socket. And
perf attributes look good.
Reported-and-tested-by: Brice Goglin <Brice.Goglin@...ia.fr>
Just one minor typo below.
Le 09/04/2019 à 23:44, Keith Busch a écrit :
> Some types of memory nodes that HMAT describes may not be online at the
> time we initially parse their nodes' tables. If the node should be set
> to online later, as can happen when using PMEM as RAM after boot, the
> node's attributes will be missing their initiator links and performance.
>
> Regsiter a memory notifier callback and set the memory attributes when
Typo regsiter->register
thanks
Brice
Powered by blists - more mailing lists