From: Philippe Gerum <rpm@xenomai.org>
To: Pierangelo Masarati <masarati@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] latency fix for 2.6.25?
Date: Wed, 18 Jun 2008 19:13:51 +0200 [thread overview]
Message-ID: <4859424F.1030400@domain.hid> (raw)
In-Reply-To: <4858E524.7040902@domain.hid>
Pierangelo Masarati wrote:
> Philippe Gerum wrote:
>
>>>> Ok, you were talking about the _previous_ implementation, right?
>>> Yes. It's been running for a few hours today, so your fix seems to be
>>> fine; in any case, the tests will run overnight, and I'll let you know
>>> tomorrow. I believe this issue could not be easily pointed out by just
>>> a simple latency check.
>>>
>> Agreed, we need to create a load that makes races on seqlocks more likely, and
>> ideally with lots of readers delaying a single writer.
>
> The testing of your fix ran overnight without problems, so we'd consider
> it fine.
Ok, thanks. Will issue -03 asap.
Another possible fix to preserve linux timings is to use
> local_irq_disable_hw() after halt. It seems to create no significant
> latency.
>
The only way to fully preserve the timings would involve running
sched_clock_idle_wakeup_event() with hw interrupts off, which grabs a spinlock
on the current runqueue; I'm worried about latencies introduced by sporadic
contention on that lock due to task migrations.
OTOH, the scheduler tick handler implements a counter-measure against underflows
of the per-runqueue clocks, so even if the RTOS preempts often or for a long
time the idling code, it should resync reasonably well. Hopefully.
--
Philippe.
prev parent reply other threads:[~2008-06-18 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 16:02 [Adeos-main] latency fix for 2.6.25? Pierangelo Masarati
2008-06-16 16:32 ` Philippe Gerum
2008-06-17 10:41 ` Pierangelo Masarati
2008-06-17 11:03 ` Philippe Gerum
2008-06-17 11:09 ` Philippe Gerum
2008-06-17 11:14 ` Philippe Gerum
2008-06-17 12:54 ` Pierangelo Masarati
2008-06-17 13:04 ` Philippe Gerum
2008-06-18 10:36 ` Pierangelo Masarati
2008-06-18 17:13 ` Philippe Gerum [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=4859424F.1030400@domain.hid \
--to=rpm@xenomai.org \
--cc=adeos-main@gna.org \
--cc=masarati@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.