All of lore.kernel.org
 help / color / mirror / Atom feed
From: xenophile <xenophile@piments.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] What is the Xenomai time limit?
Date: Tue, 29 May 2012 22:00:48 +0200	[thread overview]
Message-ID: <4FC52AF0.6040006@piments.com> (raw)
In-Reply-To: <4FC528F0.2070307@xenomai.org>

On 05/29/12 21:52, Gilles Chanteperdrix wrote:
> On 05/29/2012 09:50 PM, xenophile wrote:
>> On 05/29/12 21:41, xenomai-owner@xenomai.org wrote:
>>>
>>> On 05/29/12 16:43, Philippe Gerum wrote:
>>>>
>>>> x86-wise, there is some more issues to keep an eye on:
>>>>
>>>> - Hyperthreading (not nice to -rt requirements)
>>>> - SMI sources (causing IRQ-disabling BIOS code to be invoked directly by
>>>> special interrupts not going through the programmable interrupt
>>>> controller, so we can't block them, and don't know when they happen).
>>>> - Some graphic card adapters (causing hw stalls to favor their own
>>>> throughput)
>>>> - Some graphic card drivers, most often proprietary, disabling
>>>> interrupts for too long.
>>>> - Some cycle-hungry x86 cache invalidation instructions (wbinv).
>>>> - The legacy x86 PIT (i8254) when used, which goes through a legacy ISA
>>>> bus, as expensive as ~1.5-2.5 us for each I/O access (you need at least
>>>> two of them to program the next clock tick). Fortunately, you won't need
>>>> it on a modern x86 platform, unless really unlucky.
>>>>
>>>> Oh well, other that that, x86 is almost fine for -rt stuff.
>>>>
>>>
>>
>> So what would be the best kind of x86 hardware to use for RT?
>>
>>    Hyperthreading comes with multicore processors I think.
>>
>>    What systems least SMI code ?
>>
>>    My guess is that fast 32 bit x86 hardware like top of range AMD Athlon
>>    processors would be good (better than multicore 64 bit ) but I'm only
>>    guessing.
>>
>>    Are fast graphics cards better, so long as they can be run without
>>    proprietary drivers ?
>>
>>    I'm sure there's no hard and fast answer but can you offer any guide
>> lines?
>>
>>    Thx.
>
> The address of the mailing list is xenomai@xenomai.org, not
> xenomai-owner@xenomai.org
>

Sorry,  I got a bounce because I originally sent the msg from the wrong 
email account my end  (that bounce came from "owner").

I replied to the bounce with the correct sender,  thinking it would go 
to the list , I did not notice that it was from xenomai-owner.

So hopefully both sender and recipient are now correct and this will 
appear on the list.

Phew.







       reply	other threads:[~2012-05-29 20:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1338320469.1537.xenomai@xenomai.org>
     [not found] ` <4FC52889.8050002@piments.com>
     [not found]   ` <4FC528F0.2070307@xenomai.org>
2012-05-29 20:00     ` xenophile [this message]
     [not found] <CAKKWdtfO26_v+gQnMnu9_dkWMMQ3D7WCB_PxXa6tsSYNFEnBdQ@mail.gmail.com>
2012-05-29 13:14 ` [Xenomai] What is the Xenomai time limit? Gilles Chanteperdrix
2012-05-29 12:38 ali hagigat
2012-05-29 14:43 ` Philippe Gerum
2012-05-30 13:39   ` ali hagigat
2012-05-30 14:49     ` Philippe Gerum

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=4FC52AF0.6040006@piments.com \
    --to=xenophile@piments.com \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.