From: Paolo Mantegazza <mantegazza@domain.hid>
To: Der Herr Hofrat <der.herr@domain.hid>
Cc: Dirk Roloff <roloff@domain.hid>, adeos-main@gna.org
Subject: Re: [Adeos-main] 260 uSec latency and no idea why
Date: Fri, 12 Mar 2004 11:32:30 -0800 [thread overview]
Message-ID: <4052104E.8020308@domain.hid> (raw)
In-Reply-To: <200403120744.i2C7iI725496@domain.hid>
Der Herr Hofrat wrote:
>
> It is a software layer - no hardware prhibiting this - so if
> you have a X-server doing cli/sti in the driver or a binary driver that
> does somthing like that - they adeos can't stop it.
>
This is true also. But it is really annoying to verify it. In suspicion
of such an event I tried to disassamble a few drivers and then look for
cli/sti. It turned out there were in asm but then they where not there
in . In fact it was the disassambler that misunderstood FA/FB in
disassembling a switch table. Then I concluded that it is not a simple
matter of objdumping and seeing so gave up.
A further example: I've a nice new ATHLON machine that in alpha mode
shows very low latencies under high Linux load, but as I'm in X they
skyrockets to msecs, and that happens with both RTAI on ADEOS and on its
old legacy RTHAL.
Yours is the first case I step on such a problem with Celerons.
Paolo.
next prev parent reply other threads:[~2004-03-12 19:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 2:26 [Adeos-main] 260 uSec latency and no idea why Dirk Roloff
2004-03-11 19:04 ` Paolo Mantegazza
2004-03-12 3:22 ` Dirk Roloff
2004-03-12 7:44 ` Der Herr Hofrat
2004-03-12 17:14 ` Dirk Roloff
2004-03-12 19:32 ` Paolo Mantegazza [this message]
2004-03-12 9:52 ` Gilles Chanteperdrix
2004-03-12 10:08 ` Der Herr Hofrat
2004-03-12 17:15 ` Dirk Roloff
2004-03-12 18:45 ` Paolo Mantegazza
2004-03-12 23:00 ` Dirk Roloff
2004-03-15 8:53 ` Vitor Angelo
2004-03-18 13:11 ` Dirk Roloff
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=4052104E.8020308@domain.hid \
--to=mantegazza@domain.hid \
--cc=adeos-main@gna.org \
--cc=der.herr@domain.hid \
--cc=roloff@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.