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 15:03:14 +0100 [thread overview]
Message-ID: <1140703394.8314.59.camel@localhost.localdomain> (raw)
In-Reply-To: <43FDB910.1080402@yahoo.com.au>
Le vendredi 24 février 2006 à 00:30 +1100, Nick Piggin a écrit :
> Emmanuel Pacaud wrote:
> > 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.
> >
>
> Nothing in kernel-parameters.txt says there will be almost no activity
> on them.
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.
If a cpu is isolated from general SMP balancing and scheduling algorithm
(I know this isolation is not complete), there will be no activity on
it, no ? Unless one explicitely move one process on this cpu.
At least, that's what I've seen with my 2.6.15 vanilla kernel with
hyperthreading activated, or with distribution supplied kernel
(Scientific linux 4). With these kernels, with isolcpus=n, there's
almost no activity on cpun.
My problem is I'm not able to obtain this behaviour with a kernel.org
2.6.15 kernel, when HT is disabled, either in BIOS, kernel config or
acpi=off parameter.
Emmanuel.
(FWIW, I'm working on a RTAI setup. Use of isolcpus in the context of a
realtime setup is explained in their ISOLCPUS document:
http://cvs.gna.org/cvsweb/vulcano/README.ISOLCPUS?rev=1.6;cvsroot=rtai
)
next prev parent reply other threads:[~2006-02-23 14:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 13:21 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
2006-02-23 13:30 ` Nick Piggin
2006-02-23 14:03 ` Emmanuel Pacaud [this message]
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=1140703394.8314.59.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
all inboxes | Powered by JetHome®