From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jeff Weber <jwamsc@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] multicore: reserving core(s) for Xenomai
Date: Wed, 14 Sep 2011 19:49:52 +0200 [thread overview]
Message-ID: <4E70E940.5010500@domain.hid> (raw)
In-Reply-To: <CAAvA3H--++6D4MhP-EOcdV7mW8Dwje+OzhxRYxeNaPJY0d4ffA@mail.gmail.com>
On 09/14/2011 05:00 PM, Jeff Weber wrote:
> On Wed, Sep 14, 2011 at 8:13 AM, Gilles Chanteperdrix <
> gilles.chanteperdrix@xenomai.org> wrote:
>
>> On 09/14/2011 02:18 PM, Henri Roosen wrote:
>> [snip]
>>>
>>> What I would like to do is to run the Xenomai realtime threads on one
>>> core of the multi-core CPU. And I would like to reserve this core only
>>> for the Xenomai realtime threads.
>>>
>> [snip]
>> The kernel has an "isolcpus" option, which allows to specify which cpus
>> should not be used by Linux.
>>
>> See Documentation/kernel-parameters.txt in the linux kernel sources for
>> an explanation.
>>
>>
> I tried to do this a year ago with the kernel isolcpus option, but could not
> get this to work:
>
>> Gilles Chanteperdrix to Jeff, xenomai-help
>> Jeff wrote:
>>> What is the best method for segregating Xenomai and Linux by CPU? I was
>>> unable to do this cleanly using /proc/xenomai/affinity for Xenomai,
>>> together with the Linux isolcpus boot option. Details below.
>>
>> I have no definite answer, I have not checked. What I suspect, however,
>> is that when you try and force an affinity for a Xenomai thread, it
>> tries and apply this affinity in secondary mode, i.e. as a plain Linux
>> thread. So, will fail if the target thread is not in the "isolcpus"
>> mask. In other words, a Xenomai thread can not run on a CPU where Linux
>> threads can not run.
This explanation sounds like crap: looking at the documentation, it
seems that when using the "isolcpus" option, threads can run on an
isolated cpu if they force their affinity.
--
Gilles.
prev parent reply other threads:[~2011-09-14 17:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 12:18 [Xenomai-help] multicore: reserving core(s) for Xenomai Henri Roosen
2011-09-14 13:13 ` Kim Mathiassen
2011-09-14 13:13 ` Gilles Chanteperdrix
2011-09-14 13:23 ` Jan Kiszka
2011-09-14 14:39 ` Henry Bausley
2011-09-14 17:53 ` Jan Kiszka
2011-09-14 13:24 ` Eric Noulard
2011-09-14 13:42 ` Henri Roosen
2011-09-14 15:00 ` Jeff Weber
2011-09-14 17:49 ` Gilles Chanteperdrix [this message]
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=4E70E940.5010500@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jwamsc@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.