From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Seth Jennings <sjenning@linux.vnet.ibm.com>
Cc: Dave Hansen <dave@sr71.net>,
Nathan Fontenot <nfont@linux.vnet.ibm.com>,
Cody P Schafer <cody@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC][PATCH] drivers: base: dynamic memory block creation
Date: Wed, 14 Aug 2013 12:43:48 -0700 [thread overview]
Message-ID: <20130814194348.GB10469@kroah.com> (raw)
In-Reply-To: <1376508705-3188-1-git-send-email-sjenning@linux.vnet.ibm.com>
On Wed, Aug 14, 2013 at 02:31:45PM -0500, Seth Jennings wrote:
> Large memory systems (~1TB or more) experience boot delays on the order
> of minutes due to the initializing the memory configuration part of
> sysfs at /sys/devices/system/memory/.
Are you sure that is the problem area? Have you run perf on it?
> ppc64 has a normal memory block size of 256M (however sometimes as low
> as 16M depending on the system LMB size), and (I think) x86 is 128M. With
> 1TB of RAM and a 256M block size, that's 4k memory blocks with 20 sysfs
> entries per block that's around 80k items that need be created at boot
> time in sysfs. Some systems go up to 16TB where the issue is even more
> severe.
The x86 developers are working with larger memory sizes and they haven't
seen the problem in this area, for them it's in other places, as I
referred to in my other email.
> This patch provides a means by which users can prevent the creation of
> the memory block attributes at boot time, yet still dynamically create
> them if they are needed.
>
> This patch creates a new boot parameter, "largememory" that will prevent
> memory_dev_init() from creating all of the memory block sysfs attributes
> at boot time. Instead, a new root attribute "show" will allow
> the dynamic creation of the memory block devices.
> Another new root attribute "present" shows the memory blocks present in
> the system; the valid inputs for the "show" attribute.
You never documented any of these abi changes, which is a requirement
(not that I'm agreeing that a boot parameter is ok...)
> There was a significant amount of refactoring to allow for this but
> IMHO, the code is much easier to understand now.
Care to refactor things first, with no logical changes, and then make
your changes in a follow-on patch, so that people can actually find what
you changed in the patch?
Remember, a series of patches please, not one big "refactor and change
it all" patch.
thanks,
greg k-h
--
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:[~2013-08-14 19:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 19:31 Seth Jennings
2013-08-14 19:40 ` Greg Kroah-Hartman
2013-08-16 19:07 ` Seth Jennings
2013-08-14 19:43 ` Greg Kroah-Hartman [this message]
2013-08-14 20:05 ` Dave Hansen
2013-08-14 20:35 ` Greg Kroah-Hartman
2013-08-14 21:16 ` Seth Jennings
2013-08-14 21:37 ` Yinghai Lu
2013-08-14 21:52 ` Seth Jennings
2013-08-14 23:20 ` Yinghai Lu
2013-08-15 2:12 ` Michael Ellerman
2013-08-14 20:40 ` Nathan Fontenot
2013-08-14 20:47 ` Dave Hansen
2013-08-14 21:14 ` Seth Jennings
2013-08-14 21:36 ` Dave Hansen
2013-08-14 21:37 ` Cody P Schafer
2013-08-14 21:49 ` Dave Hansen
2013-08-15 0:01 ` Rafael J. Wysocki
2013-08-16 18:41 ` Seth Jennings
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=20130814194348.GB10469@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=cody@linux.vnet.ibm.com \
--cc=dave@sr71.net \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nfont@linux.vnet.ibm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=sjenning@linux.vnet.ibm.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