From: Mike Galbraith <efault@gmx.de>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: isolcpus question
Date: Tue, 31 Jan 2012 05:47:26 +0100 [thread overview]
Message-ID: <1327985246.6667.8.camel@marge.simson.net> (raw)
In-Reply-To: <201201302213.39672.gene.heskett@gmail.com>
On Mon, 2012-01-30 at 22:13 -0500, Gene Heskett wrote:
> Which is, is there a isolcpus troubleshooting tool?
>
> I have an app that is supposed to use the 2nd cpu on a 2 core atom system
> all by itself, and its insisting on using cpu0 when the boot command line
> has "isolcpus=1" appended to it, and apparently I am the only one with the
> problem, its working for about 200-500 others running the same software.
isolcpus=1 isolates CPU1 so no task will automatically end up using it,
but it's up to your task (or you) to move to the isolated CPU. Pin your
task to CPU1 with taskset, and all should work fine.
-Mike
next prev parent reply other threads:[~2012-01-31 4:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 3:13 isolcpus question Gene Heskett
2012-01-31 4:47 ` Mike Galbraith [this message]
2012-01-31 6:31 ` Gene Heskett
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=1327985246.6667.8.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=gene.heskett@gmail.com \
--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).