From: Martin Bligh <mbligh@mbligh.org>
To: Ashok Raj <ashok.raj@intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
shaohua.li@intel.com, linux-kernel@vger.kernel.org,
zwane@linuxpower.ca, vatsa@in.ibm.com
Subject: Re: [PATCH 0/10] bulk cpu removal support
Date: Thu, 11 May 2006 13:42:47 -0700 [thread overview]
Message-ID: <4463A1C7.6010205@mbligh.org> (raw)
In-Reply-To: <20060511102711.A15733@unix-os.sc.intel.com>
Ashok Raj wrote:
> On Thu, May 11, 2006 at 10:02:15AM -0700, Andrew Morton wrote:
>
>>OK, thanks. I'm a little surprised that this patch wasn't accompanied by a
>>problem description, really. I mean, if a single CPU offlining takes three
>>milliseconds then why bother?
>
>
> It depends on whats running at the time... with some light load, i measured
> wall clock time, i remember seeing 2 secs at times, but its been a long time
> i did that.. so take that with a pinch :-)_
>
> i will try to get those idle and load times worked out again... the best
> i have is a 16 way, if i get help from big system oems i will send the
> numbers out
Why is taking 30s to offline CPUs a problem?
M.
next prev parent reply other threads:[~2006-05-11 20:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 5:45 [PATCH 0/10] bulk cpu removal support Shaohua Li
2006-05-08 6:29 ` Nathan Lynch
2006-05-08 7:39 ` Shaohua Li
2006-05-08 6:30 ` Ashok Raj
2006-05-11 6:06 ` Andrew Morton
2006-05-11 16:53 ` Ashok Raj
2006-05-11 17:02 ` Andrew Morton
2006-05-11 17:27 ` Ashok Raj
2006-05-11 20:42 ` Martin Bligh [this message]
2006-05-11 22:09 ` Ashok Raj
2006-05-12 0:04 ` Nathan Lynch
2006-05-11 17:19 ` Nathan Lynch
2006-05-11 17:40 ` Ashok Raj
2006-05-11 19:19 ` Nathan Lynch
2006-05-11 22:17 ` Ashok Raj
-- strict thread matches above, loose matches on Subject: below --
2006-05-14 20:49 Protasevich, Natalie
2006-05-14 21:28 Protasevich, Natalie
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=4463A1C7.6010205@mbligh.org \
--to=mbligh@mbligh.org \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=vatsa@in.ibm.com \
--cc=zwane@linuxpower.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