From: Kai Bollue <mlist1@bollue.de>
To: xenomai@xenomai.org
Subject: Re: [Xenomai] shielding fully CPU or CORE
Date: Mon, 22 Jul 2013 10:00:29 +0200 [thread overview]
Message-ID: <51ECE69D.4090008@bollue.de> (raw)
In-Reply-To: <51EA4243.4020904@web.de>
On 20.07.2013 09:54, Jan Kiszka wrote:
> On 2013-07-19 11:17, Skander Bahloul wrote:
>> Dear Xenomai list members,
>>
>> On a successful instal (but without NVIDIA driver, cf my previous message), I am now starting using Xenomai.
>>
>> We need to :
>> 1* shield fully a CPU or core, against the scheduler, interruption, etc
>> 2* run a single thread on this isolated CPU or core
>>
>> Step 2 is OK with the Xenomai API.
>> But how should I achieve step 1 ?
>>
>> I did not find advice in the Xenomai documentation.
>> I guess it should be done with :
>> $ sudo shield -a 0-3 -m -1
>>
>> Do you agree ?
>> When may I find detailed info on CPU shielding ?
> With "shield fully", do you mean 99,9...% or true 100%? The latter is
> not possible with current Linux kernels, thus also not with Xenomai. For
> the former, try kernel parameter isocpus (to keep Linux off certain
> cores), possibly in combination with xeno_hal.rthal_supported_cpus (to
> limit Xenomai to those cores).
If you use an AMD CPU with "Bulldozer" / "Piledriver" architecture, for
better latencies, it helps to keep Linux off of both cores on one
module, as they share certain ressources. E.g. use isolcpus=0,1 and bind
your Xenomai task to CPU0.
Regards,
Kai
prev parent reply other threads:[~2013-07-22 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 9:17 [Xenomai] shielding fully CPU or CORE Skander Bahloul
2013-07-20 7:54 ` Jan Kiszka
2013-07-20 8:31 ` Gilles Chanteperdrix
2013-07-20 8:39 ` Jan Kiszka
2013-07-20 8:45 ` Gilles Chanteperdrix
2013-07-22 8:00 ` Kai Bollue [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=51ECE69D.4090008@bollue.de \
--to=mlist1@bollue.de \
--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.