[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181204201432.GH18167@tassilo.jf.intel.com>
Date: Tue, 4 Dec 2018 12:14:32 -0800
From: Andi Kleen <ak@...ux.intel.com>
To: Logan Gunthorpe <logang@...tatee.com>
Cc: Jerome Glisse <jglisse@...hat.com>,
Dan Williams <dan.j.williams@...el.com>,
Linux MM <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Ross Zwisler <ross.zwisler@...ux.intel.com>,
Dave Hansen <dave.hansen@...el.com>,
Haggai Eran <haggaie@...lanox.com>, balbirs@....ibm.com,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.ibm.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
"Kuehling, Felix" <felix.kuehling@....com>, Philip.Yang@....com,
"Koenig, Christian" <christian.koenig@....com>,
"Blinzer, Paul" <Paul.Blinzer@....com>,
John Hubbard <jhubbard@...dia.com>, rcampbell@...dia.com
Subject: Re: [RFC PATCH 02/14] mm/hms: heterogenenous memory system (HMS)
documentation
> Also, in the same vein, I think it's wrong to have the API enumerate all
> the different memory available in the system. The API should simply
We need an enumeration API too, just to display to the user what they
have, and possibly for applications to size their buffers
(all we do with existing NUMA nodes)
But yes the default usage should be to query for necessary attributes
-Andi
Powered by blists - more mailing lists