From: Dave Hansen <dave.hansen@intel.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
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>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH 0/7] ACPI HMAT memory sysfs representation
Date: Mon, 19 Nov 2018 09:37:51 -0800 [thread overview]
Message-ID: <c6abb754-0d82-8739-fe08-24e9402bae75@intel.com> (raw)
In-Reply-To: <b79804b0-32ee-03f9-fa62-a89684d46be6@arm.com>
On 11/18/18 9:44 PM, Anshuman Khandual wrote:
> IIUC NUMA re-work in principle involves these functional changes
>
> 1. Enumerating compute and memory nodes in heterogeneous environment (short/medium term)
This patch set _does_ that, though.
> 2. Enumerating memory node attributes as seen from the compute nodes (short/medium term)
It does that as well (a subset at least).
It sounds like the subset that's being exposed is insufficient for yo
We did that because we think doing anything but a subset in sysfs will
just blow up sysfs: MAX_NUMNODES is as high as 1024, so if we have 4
attributes, that's at _least_ 1024*1024*4 files if we expose *all*
combinations.
Do we agree that sysfs is unsuitable for exposing attributes in this manner?
next prev parent reply other threads:[~2018-11-19 17:37 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
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 [this message]
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=c6abb754-0d82-8739-fe08-24e9402bae75@intel.com \
--to=dave.hansen@intel.com \
--cc=anshuman.khandual@arm.com \
--cc=dan.j.williams@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).