mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Keith Owens <kaos@sgi.com>
Cc: ego@in.ibm.com, mingo@elte.hu, nickpiggin@yahoo.com.au,
	arjan@infradead.org, rusty@rustcorp.com.au, torvalds@osdl.org,
	akpm@osdl.org, linux-kernel@vger.kernel.org,
	arjan@intel.linux.com, davej@redhat.com, dipankar@in.ibm.com,
	vatsa@in.ibm.com, ashok.raj@intel.com
Subject: Re: [RFC][PATCH 4/4] Rename lock_cpu_hotplug/unlock_cpu_hotplug
Date: Sun, 27 Aug 2006 02:10:55 -0700	[thread overview]
Message-ID: <20060827021055.61c9d44f.pj@sgi.com> (raw)
In-Reply-To: <9747.1156668129@ocs10w.ocs.com.au>

Keith wrote:
> Updaters (which by
> definition are extremely rare) stop all other cpus, do their work then
> restart_machine().

Cpuset updaters are rare, but they are not -that- rare.

And the cpuset file system allows one to configure some
cpusets to be modifiable by any end user.

One would not want such an end user to be able to stop
the machine at will by manipulating the cpusets they
are allowed to modify.

Nor would one want the cpuset actions done by say a
batch scheduler during one jobs setup to bring all the
other presently active jobs to a grinding halt.

So perhaps taking CPUs offline merits a stop_machine().

But I've little desire to stop_machine() when modifying
cpusets.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

  reply	other threads:[~2006-08-27  9:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-24 10:34 Gautham R Shenoy
2006-08-24 11:00 ` Arjan van de Ven
2006-08-24 14:03   ` Gautham R Shenoy
2006-08-24 14:16     ` Arjan van de Ven
2006-08-24 14:55       ` Nick Piggin
2006-08-24 15:00         ` Ingo Molnar
2006-08-24 15:53           ` Nick Piggin
2006-08-25  3:53           ` Gautham R Shenoy
2006-08-27  7:59             ` Paul Jackson
2006-08-27  8:42               ` Keith Owens
2006-08-27  9:10                 ` Paul Jackson [this message]
2006-08-29 18:05               ` Paul E. McKenney
2006-08-29 19:31                 ` Paul Jackson
2006-08-29 20:03                   ` Paul E. McKenney
2006-08-30  2:38                     ` Paul Jackson
2006-08-30 15:14                       ` Paul E. McKenney
2006-08-30 17:54                         ` Paul Jackson
2006-08-30 18:13                           ` Paul E. McKenney

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=20060827021055.61c9d44f.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=arjan@intel.linux.com \
    --cc=ashok.raj@intel.com \
    --cc=davej@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=ego@in.ibm.com \
    --cc=kaos@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@osdl.org \
    --cc=vatsa@in.ibm.com \
    /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
Powered by JetHome