[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230913141136.00006a47@Huawei.com>
Date: Wed, 13 Sep 2023 14:11:36 +0100
From: Jonathan Cameron <Jonathan.Cameron@...wei.com>
To: Jinhui Guo <guojinhui.liam@...edance.com>,
<linux-kernel@...r.kernel.org>
CC: <catalin.marinas@....com>, <linux-arm-kernel@...ts.infradead.org>,
<lizefan.x@...edance.com>, <robin.murphy@....com>,
<will@...nel.org>
Subject: Re: [PATCH] arm64: cpufeature: Expose the real mpidr value to EL0
On Wed, 13 Sep 2023 18:51:33 +0800
Jinhui Guo <guojinhui.liam@...edance.com> wrote:
> > As a follow up question, is there some information that is missing from
> > current topology description? (there is lots missing but I'm curious
> > as to what might matter for your use case!)
>
> We want to know the infomation about dies to advoid memroy accessing
> across dies (some settings like 2 numa per die).
The NUMA access characteristics should give you the info you want - it's
the variation in latency and bandwidth between dies that matters, not that
they are dies. If you got really bad access characteristics across a die
that info would be equally useful.
I think it is not that this is a die that matters, but rather that there
are groups of Numa nodes with relatively small differences in access
characteristics, then others with much larger variation (and I assume
a layer above that which is inter socket which is even worse).
The info is in HMAT, but the kernel presentation of HMAT is rather limited
currently - so you may want to look at extending what is visible in sysfs
from that table.
Thanks,
Jonathan
>
> thanks,
>
> Jinhui Guo
>
Powered by blists - more mailing lists