From: Robin Holt <holt@sgi.com>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Adrian Bunk <bunk@kernel.org>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
Andi Kleen <andi@firstfloor.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Jack Steiner <steiner@sgi.com>
Subject: Do we need to call calibrate_delay() for all cores/hyperthreads on a socket?
Date: Fri, 3 Dec 2010 00:52:12 -0600 [thread overview]
Message-ID: <20101203065212.GQ6858@sgi.com> (raw)
I do not know all the different combinations of sockets, cores, and
hyperthreads out there, but it seems like all cores and their hyperthreads
on a socket should compute the same value for their calculate_delay()
function.
When booting a 4096 cpu system without specifying lpj on the command line,
we spend approximately 0.1 seconds per core/hyperthread calculating the
lpj value for that cpu.
If we were to, on the other hand, only calculate the delay value for the
first core on a socket, we would reduce the time spent booting a 4096 cpu
(256 sockets, 8 cores per socket hyperthreaded) down from nearly seven
minutes to approx 25 seconds. This seems like a very safe optimization,
but I repeat that I do not know all the different potential combinations
of socket, core, hyperthread out that. Please note these are just rough
approximations taken from memory. I am doing a couple of test boots
now without and with lpj= specified on the command line to get a more
accurate approximation.
Thanks,
Robin Holt
next reply other threads:[~2010-12-03 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 6:52 Robin Holt [this message]
2010-12-03 9:36 ` Do we need to call calibrate_delay() for all cores/hyperthreads on a socket? Andi Kleen
2010-12-03 15:09 ` Robin Holt
2010-12-03 15:41 ` Andi Kleen
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=20101203065212.GQ6858@sgi.com \
--to=holt@sgi.com \
--cc=andi@firstfloor.org \
--cc=bunk@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=venkatesh.pallipadi@intel.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