mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Nathan Lynch <ntl@pobox.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: Mon, 08 May 2006 15:39:19 +0800	[thread overview]
Message-ID: <1147073960.2760.104.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <20060508062905.GA9344@localdomain>

On Mon, 2006-05-08 at 01:29 -0500, Nathan Lynch wrote:
> 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.
> 
> Some quantification of the benefits of adding this complexity would be
> appreciated.  Like, how long does it take to offline all the cpus in a
> node serially, and how much faster is the bulk method?
This depends on the workload and I haven't a data at hand, sorry. Fast
(less tasks/timers/softirqs migration) is one benefit. The method also
means less time in stop_machine_run and less interrupt redirection, so
smaller impact to the whole system.

Thanks,
Shaohua

  reply	other threads:[~2006-05-08  7:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08  5:45 Shaohua Li
2006-05-08  6:29 ` Nathan Lynch
2006-05-08  7:39   ` Shaohua Li [this message]
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
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
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=1147073960.2760.104.camel@sli10-desk.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=akpm@osdl.org \
    --cc=ashok.raj@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntl@pobox.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

all inboxes | Powered by JetHome®