From: Ashok Raj <ashok.raj@intel.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Shaohua Li <shaohua.li@intel.com>,
linux-kernel@vger.kernel.org, zwane@linuxpower.ca,
vatsa@in.ibm.com, ashok.raj@intel.com
Subject: Re: [PATCH 0/10] bulk cpu removal support
Date: Thu, 11 May 2006 09:53:09 -0700 [thread overview]
Message-ID: <20060511095308.A15483@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060510230606.076271b2.akpm@osdl.org>; from akpm@osdl.org on Wed, May 10, 2006 at 11:06:06PM -0700
On Wed, May 10, 2006 at 11:06:06PM -0700, Andrew Morton wrote:
Hi Andrew,
> Shaohua Li <shaohua.li@intel.com> wrote:
> >
> > CPU hotremove will migrate tasks and redirect interrupts off dead cpu.
>
> This seems an awful lot of code for something which happens so infrequently.
>
> How big is the problem you're fixing here, and what are the
> user-observeable effects of these changes?
This is useful when say a NUMA node is being removed. With new multi-core
CPUs comming up, considering a 2 core with HT, we could have up to 4 logical
per socket. On NUMA node with 4 sockets, a node removal will mean we
do 16 single cpu offlines. Each time the process and interrupts could
end up on a CPU that might be removed just immediatly.
The same is also useful for SMP Suspend/resume cases since the logical offline
is same here as well.
Even thought the code changes seem a lot, most of it is just preparation of
functions ready to accept a cpumask_t instead of a single cpu like earlier.
The reason we split them to smaller chunks so the scope of change is well
understood with each patch.
The major changes are
- stop machine to run cpu offline functions on each cpu going offline
- prepare offline functions in offline path to take cpumask_t
- Some task migrate dead lock removal consideration that we ran into
during stress test.
I know Shaohua ran tests for more than 20+ hrs with the patch, both on i386
and x86_64.
once we get some time deltas on a bigger machine it will help a lot.
Iam also trying to check with some OEM';s who have such large machines for
some data.. keep posted.
ashokr
--
Cheers,
Ashok Raj
- Open Source Technology Center
next prev parent reply other threads:[~2006-05-11 16:53 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 [this message]
2006-05-11 17:02 ` Andrew Morton
2006-05-11 17:27 ` Ashok Raj
2006-05-11 20:42 ` Martin Bligh
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=20060511095308.A15483@unix-os.sc.intel.com \
--to=ashok.raj@intel.com \
--cc=akpm@osdl.org \
--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