public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Pacaud <emmanuel.pacaud@univ-poitiers.fr>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: isolcpus weirdness
Date: Thu, 23 Feb 2006 14:07:33 +0100	[thread overview]
Message-ID: <1140700054.8314.44.camel@localhost.localdomain> (raw)
In-Reply-To: <43FDA8DD.2000500@yahoo.com.au>

Le jeudi 23 février 2006 à 23:21 +1100, Nick Piggin a écrit :
> Emmanuel Pacaud wrote:
> > Hi,
> > 
> > When specifying isolcpus kernel parameters, isolated cpu is always the
> > same, not the one I asked for.
..
> > 
> > What's wrong ?
> > 
> 
> If you have 2 CPUs, and "isolate" one of them, the other is isolated
> from it. Ie. there is no difference between isolating one or the other,
> the net result is that they are isolated from each other.
> 

>From kernel-parameters.txt:

+   isolcpus=   [KNL,SMP] Isolate CPUs from the general scheduler.
+         Format: <cpu number>, ..., <cpu number>
+         This option can be used to specify one or more CPUs
+         to isolate from the general SMP balancing and scheduling
+         algorithms. The only way to move a process onto or off
+         an "isolated" CPU is via the CPU affinity syscalls.
+
+         This option is the preferred way to isolate CPUs. The
+         alternative - manually setting the CPU mask of all tasks
+         in the system can cause problems and suboptimal load
+         balancer performance.

There's a difference between isolated cpus and other cpus: by default,
there's almost no activity on isolated ones. That's what I want to be
able to do.

	Emmanuel.


  reply	other threads:[~2006-02-23 13:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 13:21 isolcpus weirdness Emmanuel Pacaud
2006-02-22 21:18 ` Frederik Deweerdt
2006-02-23  9:55   ` Emmanuel Pacaud
2006-02-23 10:00     ` Con Kolivas
2006-02-23 10:51       ` Emmanuel Pacaud
2006-02-23 11:37         ` Con Kolivas
2006-02-23 12:21 ` Nick Piggin
2006-02-23 13:07   ` Emmanuel Pacaud [this message]
2006-02-23 13:30     ` Nick Piggin
2006-02-23 14:03       ` Emmanuel Pacaud
2006-02-24  6:02         ` Nick Piggin
2006-02-24  7:44           ` Emmanuel Pacaud

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=1140700054.8314.44.camel@localhost.localdomain \
    --to=emmanuel.pacaud@univ-poitiers.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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