All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashok Raj <ashok.raj@intel.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Zwane Mwaikambo <zwane@linuxpower.ca>,
	Srivatsa Vaddagiri <vatsa@in.ibm.com>,
	Ashok Raj <ashok.raj@intel.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 0/10] bulk cpu removal support
Date: Sun, 7 May 2006 23:30:37 -0700	[thread overview]
Message-ID: <20060507233037.A20857@unix-os.sc.intel.com> (raw)
In-Reply-To: <1147067137.2760.77.camel@sli10-desk.sh.intel.com>; from shaohua.li@intel.com on Mon, May 08, 2006 at 01:45:37PM +0800

On Mon, May 08, 2006 at 01:45:37PM +0800, Shaohua Li 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.
> 

Thanks shaohua, since the initial code has been collecting dust for 
some several months now, and I never got time to finish it.

Think you forgot to cc the ia64 crowd. We tried to do it a little bit more
generic way, but some required arch assist due to some differences.

Andrew: please help stage in -mm since we would need more extensive testing
and help feedback to fix any before becomming prime time.

It would also help to check if other archs have any compile issues etc..

-- 
Cheers,
Ashok Raj
- Open Source Technology Center

  parent reply	other threads:[~2006-05-08  6:30 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 [this message]
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
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=20060507233037.A20857@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 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.