From: Ingo Molnar <mingo@elte.hu>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: George Anzinger <george@mvista.com>,
LKML <linux-kernel@vger.kernel.org>,
Doug Niehaus <niehaus@ittc.ku.edu>,
Benedikt Spranger <bene@linutronix.de>
Subject: Re: High resolution timers and BH processing on -RT
Date: Fri, 28 Jan 2005 09:24:39 +0100 [thread overview]
Message-ID: <20050128082439.GA3984@elte.hu> (raw)
In-Reply-To: <1106900411.21196.181.camel@tglx.tec.linutronix.de>
* Thomas Gleixner <tglx@linutronix.de> wrote:
> > is this due to algorithmic/PIT-programming overhead, or due to the noise
> > introduced by other, non-hard-RT timers? I'd guess the later from the
> > looks of it, but did your test introduce such noise (via networking and
> > application workloads?).
>
> Right, it's due to noise by non-RT timers, which I enforced by adding
> networking and applications.
>
> This adds random timer expires and admittedly the PIT reprogramming
> overhead is adding portions of that noise.
i havent seen your latest code - what is the basic data-structure? The
stock kernel has arrays of timers with increasing granularity and a
cascade mechanism to move timers down the arrays as they slowly expire -
but with a high-resolution API (1 usec accuracy?) how does the basic
data structure look like?
Is the "noise" due to timers expiring "at once" - but isnt it unlikely
for 'normal' timers to expire in exactly the same usec as the real
high-resolution one?
or is it that we have a 'group' of normal timers expiring, which, if
they happen to occur _just_ prior a HRT event will generate a larger
delay?
Ingo
next prev parent reply other threads:[~2005-01-28 8:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 0:13 High resolution timers and BH processing on -RT Thomas Gleixner
2005-01-28 4:43 ` Ingo Molnar
2005-01-28 8:20 ` Thomas Gleixner
2005-01-28 8:24 ` Ingo Molnar [this message]
2005-01-28 8:30 ` Thomas Gleixner
2005-01-28 8:47 ` Ingo Molnar
2005-01-28 18:34 ` George Anzinger
2005-01-28 18:51 ` Ingo Molnar
2005-01-28 18:53 ` Ingo Molnar
2005-01-31 9:12 ` Thomas Gleixner
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=20050128082439.GA3984@elte.hu \
--to=mingo@elte.hu \
--cc=bene@linutronix.de \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=niehaus@ittc.ku.edu \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).