From: Andrew Morton <akpm@osdl.org>
To: Shaohua Li <shaohua.li@intel.com>
Cc: 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: Wed, 10 May 2006 23:06:06 -0700 [thread overview]
Message-ID: <20060510230606.076271b2.akpm@osdl.org> (raw)
In-Reply-To: <1147067137.2760.77.camel@sli10-desk.sh.intel.com>
Shaohua Li <shaohua.li@intel.com> wrote:
>
> CPU hotremove will migrate tasks and redirect interrupts off dead cpu.
> To remove multiple CPUs, we should iteratively do single cpu removal.
> If tasks and interrupts are migrated to a cpu which will be soon
> removed, then we will trash tasks and interrupts again. The following
> patches allow remove several cpus one time. It's fast and avoids
> unnecessary repeated trash tasks and interrupts. This will help NUMA
> style hardware removal and SMP suspend/resume. Comments and suggestions
> are appreciated.
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?
next prev parent reply other threads:[~2006-05-11 6:11 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 [this message]
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
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=20060510230606.076271b2.akpm@osdl.org \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.