From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [RFC][PATCH 4/4] shorten overrun loops of periodic timers
Date: Wed, 16 Aug 2006 18:20:39 +0200 [thread overview]
Message-ID: <44E345D7.4070904@domain.hid> (raw)
In-Reply-To: <17635.15652.735628.299134@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1941 bytes --]
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
> > Gilles Chanteperdrix wrote:
> > > Jan Kiszka wrote:
> > > > A simple patch, just like suggested by Gilles, to avoid looping over
> > > > periodic xntimer handlers in case of overruns.
> > > >
> > > > It saves the current TSC on loop entry and uses this value later when
> > > > forwarding the timer. Is is the overhead of re-reading the TSC on all
> > > > archs negligible and should we rather go that way?
> > >
> > > >(...)
> > > > - xntimerh_date(&timer->aplink) +=
> > > > - nkpod->htimer.interval;
> > > > + while ((xntimerh_date(&timer->aplink) +=
> > > > + nkpod->htimer.interval) < now);
> > >
> > > I think you are patching the wrong addition, the one you are interested
> > > in is most probably the one at the bottom of xntimer_do_tick_aperiodic.
> > >
> >
> > Ouch, indeed. Guess I should start reading what I patch. Here comes a
> > second try.
> >
> > I'm still in favour of saving the TSC instead of re-reading it.
> > Otherwise we would have to pave the code with #ifdefs for the case
> > xnarch_get_cpu_tsc() is slow for a specific setup. Not that nice, is it?
>
> I am thinking again about this patch: some handlers need to be
> rewritten, for example the posix timers handler, because the handler
> relies on the fact that it is called for every timer expiry to compute
> the overruns count. So maybe this patch should come with the addition of
> an xntimer_getoverrun service that computes the overrun count using the
> tsc ?
>
Mmh, that gets close to hrtimer_forward now: push an overdue timer to an
expiry date that is in the future and return the number of overruns. But
do we still want this optimisation of the broken path then? It starts
getting complex, probably adding more code than it is worth. I'm
starting to vote against my own patch...
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-08-16 16:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 7:01 [Xenomai-core] [RFC][PATCH 4/4] shorten overrun loops of periodic timers Jan Kiszka
2006-08-03 17:01 ` Philippe Gerum
2006-08-03 17:26 ` Gilles Chanteperdrix
2006-08-03 18:37 ` Jan Kiszka
2006-08-16 15:43 ` Gilles Chanteperdrix
2006-08-16 16:20 ` Jan Kiszka [this message]
2006-08-16 17:22 ` Gilles Chanteperdrix
2006-08-17 7:55 ` Jan Kiszka
2006-08-17 13:03 ` Gilles Chanteperdrix
2006-08-17 13:35 ` Jan Kiszka
2006-08-18 6:09 ` 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=44E345D7.4070904@domain.hid \
--to=jan.kiszka@domain.hid \
--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.