From: trem <trem@domain.hid>
To: rpm@xenomai.org
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] port 2.6.19 x86_64 to 2.6.20
Date: Sat, 03 Mar 2007 23:24:00 +0100 [thread overview]
Message-ID: <45E9F580.3010107@domain.hid> (raw)
In-Reply-To: <1172469398.1764.79.camel@domain.hid>
Philippe Gerum wrote:
> On Mon, 2007-02-26 at 00:50 +0100, trem wrote:
>
>> Hi
>>
>> I've tried to port the 2.6.19 x86_64 adeos patch to 2.6.20. you can find
>> it here :
>> http://zarb.org/~trem/adeos-ipipe-2.6.20-x86_64-1.7-03-trem.patch
>>
>
> The good news is that moving to 2.6.20 does not seem to be too much of a
> hell. Right?
>
>
Yes, there are few conflict so it's quite easy to port xenomai to 2.6.20.
>> I can apply it with with prepare_kernel.sh (from xenomai svn), but I haven't
>> tested it yet (I mean run kernel).
>>
>> I hope this patch is good enough to be used. Otherwise, I'd be pleased
>> to fix it (maybe with a bit of help).
>>
>>
>
> We are hopefully close to have a reasonably good patch for 2.6.19. Once
> we achieve this, porting to 2.6.20 should be the next step. Thanks.
>
>
I've seen ths in the Changelog : "this closes the implementation phase
of the x86_64 port."
So I suppose that the patch for 2.6.19 is finished. I've tried it and it
works fine.
The result of latency is :
[trem@domain.hid bin]$ sudo ./latency -T 10
== Sampling period: 100 us
== Test mode: periodic user-mode task
== All results in microseconds
warming up...
RTT| 00:00:01 (periodic user-mode task, 100 us period, priority 99)
RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat
worst
RTD| 0.760| 1.073| 3.660| 0| 0.760|
3.660
RTD| 0.737| 1.063| 3.012| 0| 0.737|
3.660
RTD| 0.741| 1.083| 3.396| 0| 0.737|
3.660
RTD| 0.755| 1.088| 2.344| 0| 0.737|
3.660
RTD| 0.754| 1.093| 3.431| 0| 0.737|
3.660
RTD| 0.755| 1.089| 5.119| 0| 0.737|
5.119
RTD| 0.724| 1.091| 3.126| 0| 0.724|
5.119
RTD| 0.762| 1.089| 3.171| 0| 0.724|
5.119
RTD| 0.751| 1.097| 5.508| 0| 0.724|
5.508
---|------------|------------|------------|--------|-------------------------
RTS| 0.724| 1.085| 5.508| 0| 00:00:10/00:00:10
If I don't mistake, I see a max latency of 5us. Is it realistic ?
Now, the port to 2.6.20 is open ? we can work on ?
trem
next prev parent reply other threads:[~2007-03-03 22:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 23:50 [Adeos-main] port 2.6.19 x86_64 to 2.6.20 trem
2007-02-26 5:56 ` Philippe Gerum
2007-03-03 22:24 ` trem [this message]
2007-03-03 22:58 ` Philippe Gerum
2007-03-04 17:32 ` trem
2007-03-07 23:31 ` Philippe Gerum
2007-03-25 17:19 ` Philippe Gerum
2007-03-30 10:16 ` Paul
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=45E9F580.3010107@domain.hid \
--to=trem@domain.hid \
--cc=adeos-main@gna.org \
--cc=rpm@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.