From: David Rientjes <rientjes@google.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
drepper@gmail.com, anatol.pomozov@gmail.com, jkosina@suse.cz,
akpm@linux-foundation.org, xemul@parallels.com,
paul.gortmaker@windriver.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] drivers/base/node.c: export physical address range of given node (Re: NUMA node information for pages)
Date: Fri, 11 Apr 2014 15:13:56 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1404111513040.17724@chino.kir.corp.google.com> (raw)
In-Reply-To: <53481724.8020304@intel.com>
On Fri, 11 Apr 2014, Dave Hansen wrote:
> > So? Who cares if there are non-addressable holes in part of the span?
> > Ulrich, correct me if I'm wrong, but it seems you're looking for just a
> > address-to-nodeid mapping (or pfn-to-nodeid mapping) and aren't actually
> > expecting that there are no holes in a node for things like acpi or I/O or
> > reserved memory.
> ...
> > I think trying to represent holes and handling different memory models and
> > hotplug in special ways is complete overkill.
>
> This isn't just about memory hotplug or different memory models. There
> are systems out there today, in production, that have layouts like this:
>
> |------Node0-----|
> |------Node1-----|
>
> and this:
>
> |------Node0-----|
> |-Node1-|
>
What additional information, in your opinion, can we export to assist
userspace in making this determination that $address is on $nid?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-04-11 22:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87eh1ix7g0.fsf@x240.local.i-did-not-set--mail-host-address--so-tickle-me>
[not found] ` <533a1563.ad318c0a.6a93.182bSMTPIN_ADDED_BROKEN@mx.google.com>
[not found] ` <CAOPLpQc8R2SfTB+=BsMa09tcQ-iBNJHg+tGnPK-9EDH1M47MJw@mail.gmail.com>
[not found] ` <5343806c.100cc30a.0461.ffffc401SMTPIN_ADDED_BROKEN@mx.google.com>
[not found] ` <alpine.DEB.2.02.1404091734060.1857@chino.kir.corp.google.com>
[not found] ` <5345fe27.82dab40a.0831.0af9SMTPIN_ADDED_BROKEN@mx.google.com>
[not found] ` <alpine.DEB.2.02.1404101500280.11995@chino.kir.corp.google.com>
2014-04-11 1:35 ` Naoya Horiguchi
2014-04-11 3:03 ` Naoya Horiguchi
[not found] ` <53474709.e59ec20a.3bd5.3b91SMTPIN_ADDED_BROKEN@mx.google.com>
2014-04-11 11:00 ` David Rientjes
2014-04-11 11:43 ` Naoya Horiguchi
2014-04-11 16:24 ` Dave Hansen
2014-04-11 22:13 ` David Rientjes [this message]
2014-04-11 22:53 ` Dave Hansen
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=alpine.DEB.2.02.1404111513040.17724@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=anatol.pomozov@gmail.com \
--cc=dave.hansen@intel.com \
--cc=drepper@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=paul.gortmaker@windriver.com \
--cc=xemul@parallels.com \
/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