From: Benno Senoner <sbenno@gardena.net>
To: linux-sound@vger.kernel.org
Subject: Re: HZ > 100 overhead
Date: Wed, 27 Oct 1999 20:39:18 +0000 [thread overview]
Message-ID: <marc-linux-sound-94105770018211@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-94104909204283@msgid-missing>
On Wed, 27 Oct 1999, Paul Barton-Davis wrote:
> >> >Wouldn't you say that an HZ > 100 kernel is the cleanest solution?
> >>
> >> its the cleanest, but not the best. HZ = 1000 adds about 8% overhead
> >> to IRQ processing *all the time*.
> >
> >Are you *sure* about this? I seem to remember there was some debate
> >about that figure on linux-kernel.
>
> Ed Hall measured it, and my overall impression of Ed is that I'd trust
> him to do this correctly. what did the l-k folks think ?
It depends on your box, a P133 might suffer much more than a PII400.
On a PII400 the performance his is very little IMHO (no actual numbers)
But we can't assume that HZ\x1000 for our multimedia apps.
Therefore my proposal is the following:
(similar to Eric's proposed rtcd)
In our upcoming multimedia API we will run the audio daemon
not only for providing PCM/MIDI services but precise timers too.
This could be implemented by choosing the most efficient method
at the moment:
that means: if you are runnnig with 1ms audio buffer sizes,
instead of firing up the RTC device, use the soundcard's timer
(combined with RDTSC) , to wakeup your clients.
comments ?
Benno.
next prev parent reply other threads:[~1999-10-27 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-27 17:42 HZ > 100 overhead est
1999-10-27 18:31 ` Paul Barton-Davis
1999-10-27 18:55 ` Billy Biggs
1999-10-27 20:39 ` Benno Senoner [this message]
1999-10-27 23:59 ` Paul Barton-Davis
1999-10-28 0:16 ` Benno Senoner
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=marc-linux-sound-94105770018211@msgid-missing \
--to=sbenno@gardena.net \
--cc=linux-sound@vger.kernel.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.