From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Emmanuel Pacaud <emmanuel.pacaud@univ-poitiers.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: isolcpus weirdness
Date: Thu, 23 Feb 2006 23:21:49 +1100 [thread overview]
Message-ID: <43FDA8DD.2000500@yahoo.com.au> (raw)
In-Reply-To: <1140614487.13155.20.camel@localhost.localdomain>
Emmanuel Pacaud wrote:
> Hi,
>
> When specifying isolcpus kernel parameters, isolated cpu is always the
> same, not the one I asked for.
>
> I'm working with a dual xeon machine, with linux kernel 2.6.15
> (unpatched, from kernel.org), hyperthreading desactivated (number of cpu
> = 2). I've tried to isolate cpu1, using isolcpus, but I always end with
> cpu0 isolated, even with isolcpus=1. With invalid isolcpus argument
> (cpuid > 1), no cpu is isolated, which is ok.
>
> You'll find below content of /proc/version, /proc/cpuinfo, the output of
> dmesg, and a snapshot of top when running 3 cpuburn processes.
>
> 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.
This means that the scheduler will never automatically move a task
running on an isolated CPU to another CPU. You have to move all the
tasks manually, for example by using cpu affinity.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-02-23 12:28 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 [this message]
2006-02-23 13:07 ` Emmanuel Pacaud
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=43FDA8DD.2000500@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=emmanuel.pacaud@univ-poitiers.fr \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).