From: Prarit Bhargava <prarit@sgi.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>, Bjorn Helgaas <bjorn.helgaas@hp.com>,
Ingo Molnar <mingo@redhat.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: boot-time slowdown for measure_migration_cost
Date: Mon, 30 Jan 2006 15:43:28 -0500 [thread overview]
Message-ID: <43DE7A70.8030004@sgi.com> (raw)
In-Reply-To: <20060130200026.GA5081@agluck-lia64.sc.intel.com>
Tony,
>
>
> Might it be wise to see whether the 2% variation that I saw can be
> repeated on some other architecture? Can someone else try
> this patch and post the before/after values for migration_cost from dmesg?
>
Ask and ye shall receive ... on the 64p/64G system.
Pristine:
[ 9.942253] Brought up 64 CPUs
[ 9.942904] Total of 64 processors activated (143654.91 BogoMIPS).
[ 9.943995] build_sched_domains: start
[ 32.108439] migration_cost=0,32232,39021
[ 37.894391] build_sched_domains: end
Patched:
[ 0.001307] Calibrating delay loop... 2244.60 BogoMIPS (lpj=4489216)
[ 9.942308] Brought up 64 CPUs
[ 9.942812] Total of 64 processors activated (143654.91 BogoMIPS).
[ 18.080441] migration_cost=0,31934,38750
[ 23.865993] checking if image is initramfs... it is
P.
next prev parent reply other threads:[~2006-01-30 20:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 21:03 boot-time slowdown for measure_migration_cost Bjorn Helgaas
2006-01-30 17:21 ` Ingo Molnar
2006-01-30 18:53 ` Luck, Tony
2006-01-30 19:24 ` Ingo Molnar
2006-01-30 20:00 ` Luck, Tony
2006-01-30 20:43 ` Prarit Bhargava [this message]
2006-01-30 20:52 ` Prarit Bhargava
2006-01-30 20:43 ` John Hawkes
2006-01-30 19:26 ` Chen, Kenneth W
-- strict thread matches above, loose matches on Subject: below --
2006-01-27 21:48 Luck, Tony
2006-01-27 22:08 ` Prarit Bhargava
2006-02-01 0:50 Chuck Ebbert
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=43DE7A70.8030004@sgi.com \
--to=prarit@sgi.com \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tony.luck@intel.com \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox