From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linuxppc-dev@ozlabs.org, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [PATCH 0/8] v5 De-couple sysfs memory directories from memory sections
Date: Thu, 12 Aug 2010 13:07:03 -0700 [thread overview]
Message-ID: <1281643623.6772.78.camel@nimitz> (raw)
In-Reply-To: <20100812120816.e97d8b9e.akpm@linux-foundation.org>
On Thu, 2010-08-12 at 12:08 -0700, Andrew Morton wrote:
> > This set of patches allows for each directory created in sysfs
> > to cover more than one memory section. The default behavior for
> > sysfs directory creation is the same, in that each directory
> > represents a single memory section. A new file 'end_phys_index'
> > in each directory contains the physical_id of the last memory
> > section covered by the directory so that users can easily
> > determine the memory section range of a directory.
>
> What you're proposing appears to be a non-back-compatible
> userspace-visible change. This is a big issue!
Nathan, one thought to get around this at the moment would be to bump up
the size that we export in /sys/devices/system/memory/block_size_bytes.
I think you have already done most of the hard work to accomplish
this.
You can still add the end_phys_index stuff. But, for now, it would
always be equal to start_phys_index.
-- Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nathan Fontenot <nfont@austin.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linuxppc-dev@ozlabs.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Greg KH <greg@kroah.com>
Subject: Re: [PATCH 0/8] v5 De-couple sysfs memory directories from memory sections
Date: Thu, 12 Aug 2010 13:07:03 -0700 [thread overview]
Message-ID: <1281643623.6772.78.camel@nimitz> (raw)
In-Reply-To: <20100812120816.e97d8b9e.akpm@linux-foundation.org>
On Thu, 2010-08-12 at 12:08 -0700, Andrew Morton wrote:
> > This set of patches allows for each directory created in sysfs
> > to cover more than one memory section. The default behavior for
> > sysfs directory creation is the same, in that each directory
> > represents a single memory section. A new file 'end_phys_index'
> > in each directory contains the physical_id of the last memory
> > section covered by the directory so that users can easily
> > determine the memory section range of a directory.
>
> What you're proposing appears to be a non-back-compatible
> userspace-visible change. This is a big issue!
Nathan, one thought to get around this at the moment would be to bump up
the size that we export in /sys/devices/system/memory/block_size_bytes.
I think you have already done most of the hard work to accomplish
this.
You can still add the end_phys_index stuff. But, for now, it would
always be equal to start_phys_index.
-- Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nathan Fontenot <nfont@austin.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linuxppc-dev@ozlabs.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Greg KH <greg@kroah.com>
Subject: Re: [PATCH 0/8] v5 De-couple sysfs memory directories from memory sections
Date: Thu, 12 Aug 2010 13:07:03 -0700 [thread overview]
Message-ID: <1281643623.6772.78.camel@nimitz> (raw)
In-Reply-To: <20100812120816.e97d8b9e.akpm@linux-foundation.org>
On Thu, 2010-08-12 at 12:08 -0700, Andrew Morton wrote:
> > This set of patches allows for each directory created in sysfs
> > to cover more than one memory section. The default behavior for
> > sysfs directory creation is the same, in that each directory
> > represents a single memory section. A new file 'end_phys_index'
> > in each directory contains the physical_id of the last memory
> > section covered by the directory so that users can easily
> > determine the memory section range of a directory.
>
> What you're proposing appears to be a non-back-compatible
> userspace-visible change. This is a big issue!
Nathan, one thought to get around this at the moment would be to bump up
the size that we export in /sys/devices/system/memory/block_size_bytes.
I think you have already done most of the hard work to accomplish
this.
You can still add the end_phys_index stuff. But, for now, it would
always be equal to start_phys_index.
-- 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:[~2010-08-12 20:07 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 17:53 [PATCH 0/8] v5 De-couple sysfs memory directories from memory sections Nathan Fontenot
2010-08-09 17:53 ` Nathan Fontenot
2010-08-09 17:53 ` Nathan Fontenot
2010-08-09 18:35 ` [PATCH 1/8] v5 Move the find_memory_block() routine up Nathan Fontenot
2010-08-09 18:35 ` Nathan Fontenot
2010-08-09 18:35 ` Nathan Fontenot
2010-08-09 18:36 ` [PATCH 2/8] v5 Add new phys_index properties Nathan Fontenot
2010-08-09 18:36 ` Nathan Fontenot
2010-08-09 18:36 ` Nathan Fontenot
2010-08-09 18:37 ` [PATCH 3/8] v5 Add section count to memory_block Nathan Fontenot
2010-08-09 18:37 ` Nathan Fontenot
2010-08-09 18:37 ` Nathan Fontenot
2010-08-09 18:38 ` [PATCH 4/8] v5 Add mutex for add/remove of memory blocks Nathan Fontenot
2010-08-09 18:38 ` Nathan Fontenot
2010-08-09 18:38 ` Nathan Fontenot
2010-08-09 18:39 ` [PATCH 5/8] v5 Allow memory_block to span multiple memory sections Nathan Fontenot
2010-08-09 18:39 ` Nathan Fontenot
2010-08-09 18:39 ` Nathan Fontenot
2010-08-09 18:41 ` [PATCH 6/8] v5 Update the node sysfs code Nathan Fontenot
2010-08-09 18:41 ` Nathan Fontenot
2010-08-09 18:41 ` Nathan Fontenot
2010-08-09 18:42 ` [PATCH 7/8] v5 Define memory_block_size_bytes() for ppc/pseries Nathan Fontenot
2010-08-09 18:42 ` Nathan Fontenot
2010-08-09 18:42 ` Nathan Fontenot
2010-08-09 18:43 ` [PATCH 8/8] v5 Update memory-hotplug documentation Nathan Fontenot
2010-08-09 18:43 ` Nathan Fontenot
2010-08-09 18:43 ` Nathan Fontenot
2010-08-09 20:44 ` Nishanth Aravamudan
2010-08-09 20:44 ` Nishanth Aravamudan
2010-08-09 20:44 ` Nishanth Aravamudan
2010-08-09 20:48 ` Nishanth Aravamudan
2010-08-09 20:48 ` Nishanth Aravamudan
2010-08-10 12:17 ` Nathan Fontenot
2010-08-10 12:17 ` Nathan Fontenot
2010-08-10 12:17 ` Nathan Fontenot
2010-08-11 15:18 ` [PATCH 0/8] v5 De-couple sysfs memory directories from memory sections Dave Hansen
2010-08-11 15:18 ` Dave Hansen
2010-08-11 15:18 ` Dave Hansen
2010-08-12 19:08 ` Andrew Morton
2010-08-12 19:08 ` Andrew Morton
2010-08-12 19:08 ` Andrew Morton
2010-08-12 20:07 ` Dave Hansen [this message]
2010-08-12 20:07 ` Dave Hansen
2010-08-12 20:07 ` Dave Hansen
2010-08-16 14:34 ` Nathan Fontenot
2010-08-16 14:34 ` Nathan Fontenot
2010-08-16 14:34 ` Nathan Fontenot
2010-08-31 18:12 ` Dave Hansen
2010-08-31 18:12 ` Dave Hansen
2010-08-31 18:12 ` Dave Hansen
2010-08-31 21:57 ` Anton Blanchard
2010-08-31 21:57 ` Anton Blanchard
2010-08-31 21:57 ` Anton Blanchard
2010-09-02 17:39 ` Nathan Fontenot
2010-09-02 17:39 ` Nathan Fontenot
2010-09-02 17:39 ` Nathan Fontenot
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=1281643623.6772.78.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.