From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Keith Busch <keith.busch@intel.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-mm@kvack.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rafael Wysocki <rafael@kernel.org>,
Dave Hansen <dave.hansen@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH 0/7] ACPI HMAT memory sysfs representation
Date: Fri, 16 Nov 2018 11:57:58 +0530 [thread overview]
Message-ID: <1ed406b2-b85f-8e02-1df0-7c39aa21eca9@arm.com> (raw)
In-Reply-To: <20181114224902.12082-1-keith.busch@intel.com>
On 11/15/2018 04:19 AM, Keith Busch wrote:
> This series provides a new sysfs representation for heterogeneous
> system memory.
>
> The previous series that was specific to HMAT that this series was based
> on was last posted here: https://lkml.org/lkml/2017/12/13/968
>
> Platforms may provide multiple types of cpu attached system memory. The
> memory ranges for each type may have different characteristics that
> applications may wish to know about when considering what node they want
> their memory allocated from.
>
> It had previously been difficult to describe these setups as memory
> rangers were generally lumped into the NUMA node of the CPUs. New
> platform attributes have been created and in use today that describe
> the more complex memory hierarchies that can be created.
>
> This series first creates new generic APIs under the kernel's node
> representation. These new APIs can be used to create links among local
> memory and compute nodes and export characteristics about the memory
> nodes. Documentation desribing the new representation are provided.
>
> Finally the series adds a kernel user for these new APIs from parsing
> the ACPI HMAT.
Not able to see the patches from this series either on the list or on the
archive (https://lkml.org/lkml/2018/11/15/331). IIRC last time we discussed
about this and the concern which I raised was in absence of a broader NUMA
rework for multi attribute memory it might not a good idea to settle down
and freeze sysfs interface for the user space.
next prev parent reply other threads:[~2018-11-16 6:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 22:49 [PATCH 0/7] ACPI HMAT memory sysfs representation Keith Busch
2018-11-16 6:27 ` Anshuman Khandual [this message]
2018-11-16 15:51 ` Keith Busch
2018-11-19 1:52 ` Anshuman Khandual
2018-11-16 16:55 ` Dave Hansen
2018-11-19 5:44 ` Anshuman Khandual
2018-11-19 17:37 ` Dave Hansen
2018-11-22 11:52 ` Anshuman Khandual
2018-11-22 18:01 ` Dave Hansen
2018-11-23 6:42 ` Anshuman Khandual
2018-11-23 19:21 ` Dave Hansen
2018-11-23 21:13 ` Dan Williams
2018-11-26 15:52 ` Anshuman Khandual
2018-11-26 16:42 ` Dave Hansen
2018-11-26 18:08 ` Dan Williams
2018-11-27 10:15 ` Anshuman Khandual
2018-11-27 16:56 ` Dan Williams
2018-11-26 15:38 ` Anshuman Khandual
2018-11-26 17:20 ` Dave Hansen
2018-11-27 9:32 ` Anshuman Khandual
2018-11-22 18:08 ` Dan Williams
2018-11-23 7:10 ` Anshuman Khandual
2018-11-23 17:15 ` Dan Williams
2018-11-27 14:05 ` Anshuman Khandual
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1ed406b2-b85f-8e02-1df0-7c39aa21eca9@arm.com \
--to=anshuman.khandual@arm.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=keith.busch@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rafael@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).