From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Gary Hade <garyhade@us.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
y-goto@jp.fujitsu.com, pbadari@us.ibm.com, mel@csn.ul.ie,
lcm@us.ibm.com, mingo@elte.hu, greg@kroah.com,
nish.aravamudan@gmail.com
Subject: Re: [PATCH 1/2] [REPOST] mm: show node to memory section relationship with symlinks in sysfs
Date: Mon, 13 Oct 2008 09:40:35 -0700 [thread overview]
Message-ID: <1223916035.29877.10.camel@nimitz> (raw)
In-Reply-To: <20081013163416.GA7340@us.ibm.com>
On Mon, 2008-10-13 at 09:34 -0700, Gary Hade wrote:
> I understand your concerns about adding possibly frivolous interfaces
> but in this case we are simply eliminating a very obvious hole in the
> existing set of memory hot-add/remove interfaces. In general, it
> makes absolutely no sense to provide a resource add/remove mechanism
> without telling the user where the resource is physically located.
Does it help we export the phys_index (basically the section number) as
part of the section directory?
I don't think we export the physical memory ranges of NUMA nodes. But,
if we did that as well, it would allow userspace to do this association
without troubling the kernel with maintaining it.
-- Dave
--
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:[~2008-10-13 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 19:21 Gary Hade
2008-10-10 10:55 ` Yasunori Goto
2008-10-10 19:42 ` Andrew Morton
2008-10-10 21:33 ` Gary Hade
2008-10-10 21:59 ` Andrew Morton
2008-10-10 23:18 ` Gary Hade
2008-10-10 23:32 ` Andrew Morton
2008-10-13 16:34 ` Gary Hade
2008-10-13 16:40 ` Dave Hansen [this message]
2008-10-14 11:54 ` Yasunori Goto
2008-10-14 21:06 ` Gary Hade
2008-10-15 10:37 ` Yasunori Goto
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=1223916035.29877.10.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=garyhade@us.ibm.com \
--cc=greg@kroah.com \
--cc=lcm@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mingo@elte.hu \
--cc=nish.aravamudan@gmail.com \
--cc=pbadari@us.ibm.com \
--cc=y-goto@jp.fujitsu.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