From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org, Stuart O Anderson <soa@domain.hid>
Subject: Re: [Xenomai-help] Known-to-work motherboards?
Date: Thu, 12 Feb 2009 23:59:59 +0100 [thread overview]
Message-ID: <4994A9EF.9070108@domain.hid> (raw)
In-Reply-To: <4994A261.5050003@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Gilles Chanteperdrix wrote:
>>> Jan Kiszka wrote:
>>>> Gilles Chanteperdrix wrote:
>>>>> Stuart O Anderson wrote:
>>>>>> If there isn't a list online that I've missed, is anyone running
>>>>>> xenomai on a relatively recent machine with 8 or more cores without
>>>>>> problems? If so, can you provide hardware specs?
>>>>> Xenomai will have scalability problems when running on an 8 cores system
>>>>> (if you intend to run real-time tasks on each of the 8 cores).
>>>>>
>>>> We are running Xenomai on up to 4x4 boxes, but only with 1 or 2 cores
>>>> used by RT tasks. I've some patch hanging around that restricts Xenomai
>>>> (specifically its host timer hook) to a CPU subset in order to mitigate
>>>> the scalability issues - guess I should finally get it in shape and post it.
>>> The host timer already runs on only one CPU.
>> Not on x86.
>
> Some time ago, when using the APIC (which was always the case on x86
> SMP), the host timer was not even started, and the Linux APIC irqs were
> triggered by a custom 8254 irq handler. Well, it seems things have
> changed since then...
...around the Linux clocksource/clockevent rework. And it also makes
more sense with the number of cores increasing and NUMA becoming
standard. CPU-local timers are simply more efficient. That's why the
nklock hurts that any host tick must pass even if the core is not used
by Xenomai otherwise.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
prev parent reply other threads:[~2009-02-12 22:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 17:04 [Xenomai-help] Known-to-work motherboards? Stuart O Anderson
2009-02-12 20:05 ` Gilles Chanteperdrix
2009-02-12 21:02 ` Jan Kiszka
2009-02-12 22:10 ` Gilles Chanteperdrix
2009-02-12 22:24 ` Jan Kiszka
2009-02-12 22:27 ` Gilles Chanteperdrix
2009-02-12 22:59 ` Jan Kiszka [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=4994A9EF.9070108@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=soa@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.