From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gregory CLEMENT <gclement00@domain.hid>
Cc: Xenomai-core@domain.hid
Subject: Re: [Xenomai-core] RTOS porting on ARM
Date: Tue, 09 Oct 2007 11:45:49 +0200 [thread overview]
Message-ID: <470B4DCD.4000303@domain.hid> (raw)
In-Reply-To: <305035a40710090235g54c57436u770168437f27a7f6@domain.hid>
Gregory CLEMENT wrote:
> 2007/10/9, Jan Kiszka <jan.kiszka@domain.hid>:
>> Gilles Chanteperdrix wrote:
>>> gclement00 at gmail.com (Gregory CLEMENT) wrote:
>>> >
>>> > For RTAI we have now a working systeme with have better max latency
>>> > than Xenomai ( 50us instead of around 100us for Xenomai). I plan to
>>> > update the patches on our site with this new version and communicate
>>> > on it on RTAI list as soon as I have some free time.
>>>
>>> A good place for discussing about these figures would have been Xenomai
>>> mailing list, a place where we could have answered you immediately. Are
>>> you sure you are not comparing Xenomai user-space scheduling latency
>>> with RTAI kernel-space scheduling latency ?
>> Me too asked Gregory for some discussion on this long ago but received
>> no response.
>>
>> Anyway, the critical thing beyond latencies remains *maintenance*. If
>> someone decides to apply I-pipe on RTAI *and* doesn't forget to
>> contribute to the mandatory bits of the Adeos project, work actively
>> within that community (test new versions and report results, track down
>> bugs, port to new kernels releases, etc.), anyone would benefit in the
>> end. BTW, that would surely stimulate discussions about differing
>> numbers on both sides as well.
>
> And you think we didn't contribute to adeos projects, test new version
> and report result???
> Because it is exactly what we have done.
You did this for the startup of this port, and it is highly appreciated.
But such things require lasting effort. Probably I'm just so sceptical
because there have been many people before posting patches once and then
never again. Just look at RTAI's ARM history of the last, mmh, 4 years.
I'm always happy being proved wrong regarding such scepticisms of mine!
> Our result on RTAI are pretty recent, and the lack of discussion on it
> is only a lack of time and not a lack of wiling.
Then I'm looking forward to have this now, e.g. backed up with tracer
outputs of both variants.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2007-10-09 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <515338.44993.qm@domain.hid>
[not found] ` <80b317760709110456k2ef95162t19d833da7c5781de@domain.hid>
[not found] ` <46E699C6.80609@domain.hid>
[not found] ` <305035a40709140817q452ca77dude2af88ce6fc3dd9@domain.hid>
2007-10-09 7:28 ` [Xenomai-core] RTOS porting on ARM Gilles Chanteperdrix
[not found] ` <305035a40710082339t16c75581sd07c7f05ed7df9c2@domain.hid>
2007-10-09 7:25 ` Gilles Chanteperdrix
[not found] ` <305035a40710090103n7f14377ema39ed8aab42207a6@domain.hid>
2007-10-09 8:46 ` Gilles Chanteperdrix
2007-10-09 9:09 ` Gregory CLEMENT
2007-10-09 9:32 ` Gilles Chanteperdrix
2007-10-09 9:14 ` Jan Kiszka
[not found] ` <305035a40710090235g54c57436u770168437f27a7f6@domain.hid>
2007-10-09 9:45 ` Jan Kiszka [this message]
2007-10-09 10:41 ` Gregory CLEMENT
2007-10-09 12:41 ` Jan Kiszka
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=470B4DCD.4000303@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Xenomai-core@domain.hid \
--cc=gclement00@domain.hid \
/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.