From: Robin Holt <holt@sgi.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
Badari Pulavarty <pbadari@us.ibm.com>,
Dave Hansen <haveblue@us.ibm.com>,
Gary Hade <garyhade@us.ibm.com>, Ingo Molnar <mingo@elte.hu>,
Matt Tolentino <matthew.e.tolentino@intel.com>,
"Robert P. J. Day" <rpjday@crashcourse.ca>
Subject: [Patch 0/3] Speed up link_mem_sections during boot.
Date: Wed, 29 Sep 2010 14:00:53 -0500 [thread overview]
Message-ID: <20100929190053.992911934@gulag1.americas.sgi.com> (raw)
During boot of a large system, we see a delay in the portion of boot which
is calling link_mem_sections(). On a 16TB x86_64 system, it is taking
1 hour 27 minutes. With this patch set applied, it takes 46 seconds.
The speedup is accomplished by simply caching the results from the
previous find_memory_block and using that as a quick check to see if
the next block happens to be adjacent to the previous. In our testing,
that was true 100% of the time.
---
drivers/base/memory.c | 28 ++++++++++++++++++----------
drivers/base/node.c | 8 +++++---
include/linux/kobject.h | 2 ++
include/linux/memory.h | 2 ++
lib/kobject.c | 39 +++++++++++++++++++++++++++++++++++++++
5 files changed, 66 insertions(+), 13 deletions(-)
next reply other threads:[~2010-09-29 19:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 19:00 Robin Holt [this message]
2010-09-29 19:00 ` [Patch 1/3] Introduce kset_find_obj_hinted Robin Holt
2010-09-29 20:59 ` Dave Hansen
2010-09-29 21:44 ` Robin Holt
2010-09-30 1:59 ` KAMEZAWA Hiroyuki
2010-09-29 19:00 ` [Patch 2/3] Introduce find_memory_block_hinted which utilizes kset_find_obj_hinted Robin Holt
2010-09-30 2:00 ` KAMEZAWA Hiroyuki
2010-09-29 19:00 ` [Patch 3/3] Convert link_mem_sections to use find_memory_block_hinted Robin Holt
2010-09-30 2:01 ` KAMEZAWA Hiroyuki
2010-10-05 23:18 ` patch "driver core: Convert link_mem_sections to use find_memory_block_hinted." added to gregkh-2.6 tree gregkh
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=20100929190053.992911934@gulag1.americas.sgi.com \
--to=holt@sgi.com \
--cc=garyhade@us.ibm.com \
--cc=gregkh@suse.de \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=mingo@elte.hu \
--cc=pbadari@us.ibm.com \
--cc=rpjday@crashcourse.ca \
/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
all inboxes | Powered by JetHome®