[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87mv2cfdnj.fsf@concordia.ellerman.id.au>
Date: Thu, 21 Dec 2017 23:50:40 +1100
From: Michael Ellerman <mpe@...erman.id.au>
To: Matthew Wilcox <willy@...radead.org>,
Ross Zwisler <ross.zwisler@...ux.intel.com>
Cc: Michal Hocko <mhocko@...nel.org>,
"Box\, David E" <david.e.box@...el.com>,
Dave Hansen <dave.hansen@...el.com>,
"Zheng\, Lv" <lv.zheng@...el.com>, linux-nvdimm@...ts.01.org,
"Verma\, Vishal L" <vishal.l.verma@...el.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
"Anaczkowski\, Lukasz" <lukasz.anaczkowski@...el.com>,
"Moore\, Robert" <robert.moore@...el.com>,
linux-acpi@...r.kernel.org,
"Odzioba\, Lukasz" <lukasz.odzioba@...el.com>,
"Schmauss\, Erik" <erik.schmauss@...el.com>,
Len Brown <lenb@...nel.org>,
John Hubbard <jhubbard@...dia.com>,
linuxppc-dev@...ts.ozlabs.org, Jerome Glisse <jglisse@...hat.com>,
Dan Williams <dan.j.williams@...el.com>, devel@...ica.org,
"Kogut\, Jaroslaw" <Jaroslaw.Kogut@...el.com>, linux-mm@...ck.org,
"Koss\, Marcin" <marcin.koss@...el.com>, linux-api@...r.kernel.org,
Brice Goglin <brice.goglin@...il.com>,
"Nachimuthu\, Murugasamy" <murugasamy.nachimuthu@...el.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
linux-kernel@...r.kernel.org,
"Koziej\, Artur" <artur.koziej@...el.com>,
"Lahtinen\, Joonas" <joonas.lahtinen@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Tim Chen <tim.c.chen@...ux.intel.com>
Subject: Re: [PATCH v3 0/3] create sysfs representation of ACPI HMAT
Matthew Wilcox <willy@...radead.org> writes:
> On Mon, Dec 18, 2017 at 01:35:47PM -0700, Ross Zwisler wrote:
>> What I'm hoping to do with this series is to just provide a sysfs
>> representation of the HMAT so that applications can know which NUMA nodes to
>> select with existing utilities like numactl. This series does not currently
>> alter any kernel behavior, it only provides a sysfs interface.
>>
>> Say for example you had a system with some high bandwidth memory (HBM), and
>> you wanted to use it for a specific application. You could use the sysfs
>> representation of the HMAT to figure out which memory target held your HBM.
>> You could do this by looking at the local bandwidth values for the various
>> memory targets, so:
>>
>> # grep . /sys/devices/system/hmat/mem_tgt*/local_init/write_bw_MBps
>> /sys/devices/system/hmat/mem_tgt2/local_init/write_bw_MBps:81920
>> /sys/devices/system/hmat/mem_tgt3/local_init/write_bw_MBps:40960
>> /sys/devices/system/hmat/mem_tgt4/local_init/write_bw_MBps:40960
>> /sys/devices/system/hmat/mem_tgt5/local_init/write_bw_MBps:40960
>>
>> and look for the one that corresponds to your HBM speed. (These numbers are
>> made up, but you get the idea.)
>
> Presumably ACPI-based platforms will not be the only ones who have the
> ability to expose different bandwidth memories in the future. I think
> we need a platform-agnostic way ... right, PowerPC people?
Yes!
I don't have any detail at hand but will try and rustle something up.
cheers
Powered by blists - more mailing lists