From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: rientjes@google.com
Cc: 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 07:43:11 -0400 [thread overview]
Message-ID: <5347e178.b5138c0a.3d90.ffffc373SMTPIN_ADDED_BROKEN@mx.google.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1404110325210.30610@chino.kir.corp.google.com>
On Fri, Apr 11, 2014 at 04:00:20AM -0700, David Rientjes wrote:
> On Thu, 10 Apr 2014, Naoya Horiguchi wrote:
>
> > Yes, that's right, but it seems to me that just node_start_pfn and node_end_pfn
> > is not enough because there can be holes (without any page struct backed) inside
> > [node_start_pfn, node_end_pfn), and it's not aware of memory hotplug.
> >
>
> 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.
>
> The node spans a contiguous length of memory, there's no consideration for
> addresses that aren't actually backed by physical memory. We are just
> representing proximity domains that have a base address and length in the
> acpi world.
>
> Memory hotplug is already taken care of because onlining and offlining
> nodes already add these node classes and {start,end}_phys_addr would
> show up automatically. If you use node_start_pfn(nid) and
> node_end_pfn(nid) as suggested, there's no futher consideration needed for
> hotplug.
>
> I think trying to represent holes and handling different memory models and
> hotplug in special ways is complete overkill.
OK, I agree to your idea.
Your patch looks good to me.
Thanks,
Naoya Horiguchi
> Ulrich, can I have your ack?
> ---
> Documentation/ABI/stable/sysfs-devices-node | 12 ++++++++++++
> drivers/base/node.c | 18 ++++++++++++++++++
> 2 files changed, 30 insertions(+)
>
> diff --git a/Documentation/ABI/stable/sysfs-devices-node b/Documentation/ABI/stable/sysfs-devices-node
> --- a/Documentation/ABI/stable/sysfs-devices-node
> +++ b/Documentation/ABI/stable/sysfs-devices-node
> @@ -63,6 +63,18 @@ Description:
> The node's hit/miss statistics, in units of pages.
> See Documentation/numastat.txt
>
> +What: /sys/devices/system/node/nodeX/start_phys_addr
> +Date: April 2014
> +Contact: David Rientjes <rientjes@google.com>
> +Description:
> + The physical base address of this node.
> +
> +What: /sys/devices/system/node/nodeX/end_phys_addr
> +Date: April 2014
> +Contact: David Rientjes <rientjes@google.com>
> +Description:
> + The physical base + length address of this node.
> +
> What: /sys/devices/system/node/nodeX/distance
> Date: October 2002
> Contact: Linux Memory Management list <linux-mm@kvack.org>
> diff --git a/drivers/base/node.c b/drivers/base/node.c
> --- a/drivers/base/node.c
> +++ b/drivers/base/node.c
> @@ -170,6 +170,20 @@ static ssize_t node_read_numastat(struct device *dev,
> }
> static DEVICE_ATTR(numastat, S_IRUGO, node_read_numastat, NULL);
>
> +static ssize_t node_read_start_phys_addr(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
> + return sprintf(buf, "0x%lx\n", node_start_pfn(dev->id) << PAGE_SHIFT);
> +}
> +static DEVICE_ATTR(start_phys_addr, S_IRUGO, node_read_start_phys_addr, NULL);
> +
> +static ssize_t node_read_end_phys_addr(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
> + return sprintf(buf, "0x%lx\n", node_end_pfn(dev->id) << PAGE_SHIFT);
> +}
> +static DEVICE_ATTR(end_phys_addr, S_IRUGO, node_read_end_phys_addr, NULL);
> +
> static ssize_t node_read_vmstat(struct device *dev,
> struct device_attribute *attr, char *buf)
> {
> @@ -286,6 +300,8 @@ static int register_node(struct node *node, int num, struct node *parent)
> device_create_file(&node->dev, &dev_attr_cpulist);
> device_create_file(&node->dev, &dev_attr_meminfo);
> device_create_file(&node->dev, &dev_attr_numastat);
> + device_create_file(&node->dev, &dev_attr_start_phys_addr);
> + device_create_file(&node->dev, &dev_attr_end_phys_addr);
> device_create_file(&node->dev, &dev_attr_distance);
> device_create_file(&node->dev, &dev_attr_vmstat);
>
> @@ -311,6 +327,8 @@ void unregister_node(struct node *node)
> device_remove_file(&node->dev, &dev_attr_cpulist);
> device_remove_file(&node->dev, &dev_attr_meminfo);
> device_remove_file(&node->dev, &dev_attr_numastat);
> + device_remove_file(&node->dev, &dev_attr_start_phys_addr);
> + device_remove_file(&node->dev, &dev_attr_end_phys_addr);
> device_remove_file(&node->dev, &dev_attr_distance);
> device_remove_file(&node->dev, &dev_attr_vmstat);
>
>
> --
> 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>
>
--
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 12:35 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 [this message]
2014-04-11 16:24 ` Dave Hansen
2014-04-11 22:13 ` David Rientjes
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=5347e178.b5138c0a.3d90.ffffc373SMTPIN_ADDED_BROKEN@mx.google.com \
--to=n-horiguchi@ah.jp.nec.com \
--cc=akpm@linux-foundation.org \
--cc=anatol.pomozov@gmail.com \
--cc=drepper@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paul.gortmaker@windriver.com \
--cc=rientjes@google.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