From: george anzinger <george@mvista.com>
To: Joe deBlaquiere <jadb@redhat.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
yodaiken@fsmlabs.com, Andrew Morton <andrewm@uow.edu.au>,
Nigel Gamble <nigel@nrg.org>,
linux-kernel@vger.kernel.org,
linux-audio-dev@ginette.musique.umontreal.ca
Subject: Re: [linux-audio-dev] low-latency scheduling patch for 2.4.0
Date: Tue, 30 Jan 2001 23:55:46 -0800 [thread overview]
Message-ID: <3A77C502.4010504@mvista.com> (raw)
In-Reply-To: <3A75A70C.4050205@redhat.com> <200101220150.UAA29623@renoir.op.net> <Pine.LNX.4.05.10101211754550.741-100000@cosmic.nrg.org>, <Pine.LNX.4.05.10101211754550.741-100000@cosmic.nrg.org>; <20010128061428.A21416@hq.fsmlabs.com> <3A742A79.6AF39EEE@uow.edu.au> <3A74462A.80804@redhat.com> <20010129084410.B32652@hq.fsmlabs.com> <30672.980867280@redhat.com> <3A76E155.2030905@redhat.com>
Joe deBlaquiere wrote:
~snip~
> The locical answer is run with HZ=10000 so you get 100us intervals,
> right ;o).
Lets not assume we need the overhead of HZ=10000 to get 100us
alarm/timer resolution. How about a timer that ticks when we need the
next tick...
On systems with multiple hardware timers you could kick off a
> single event at 200us, couldn't you? I've done that before with the
> extra timer assigned exclusively to a resource.
With the right hardware resource, one high res counter can give you all
the various tick resolutions you need. BTDT on HPRT.
George
It's not a giant time
> slice, but at least you feel like you're allowing something to happen,
> right?
>
>>
>> --
>> dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-31 7:59 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 2:53 low-latency scheduling patch for 2.4.0 Andrew Morton
2001-01-11 3:12 ` [linux-audio-dev] " Jay Ts
2001-01-11 3:22 ` Cort Dougan
2001-01-11 12:38 ` Alan Cox
2001-01-11 11:30 ` Andrew Morton
2001-01-11 5:19 ` David S. Miller
2001-01-11 13:57 ` Daniel Phillips
2001-01-11 20:55 ` Nigel Gamble
2001-01-11 21:31 ` David S. Miller
2001-01-15 5:27 ` george anzinger
2001-01-12 13:30 ` Andrew Morton
2001-01-12 15:11 ` Tim Wright
2001-01-12 22:30 ` Nigel Gamble
2001-01-13 1:01 ` Andrew Morton
2001-01-15 19:46 ` Tim Wright
2001-01-12 22:46 ` Nigel Gamble
2001-01-12 23:08 ` george anzinger
2001-01-21 0:05 ` yodaiken
2001-01-22 0:54 ` Nigel Gamble
2001-01-22 1:49 ` Paul Barton-Davis
2001-01-22 2:21 ` Nigel Gamble
2001-01-22 3:31 ` J Sloan
2001-01-28 13:14 ` yodaiken
2001-01-28 14:07 ` Bill Huey
2001-01-28 14:26 ` Andrew Morton
2001-01-29 5:02 ` yodaiken
2001-01-28 14:19 ` Andrew Morton
2001-01-28 16:17 ` Joe deBlaquiere
2001-01-29 15:44 ` yodaiken
2001-01-29 17:23 ` Joe deBlaquiere
2001-01-29 17:38 ` yodaiken
2001-01-29 18:03 ` Joe deBlaquiere
2001-01-30 15:08 ` David Woodhouse
2001-01-30 15:44 ` Joe deBlaquiere
2001-01-30 16:29 ` Paul Davis
2001-01-30 16:35 ` David Woodhouse
2001-01-31 7:55 ` george anzinger [this message]
2001-01-30 16:19 ` David Woodhouse
2001-02-01 12:40 ` Pavel Machek
2001-02-01 22:33 ` David Woodhouse
2001-02-02 4:17 ` Joe deBlaquiere
2001-01-30 20:51 ` yodaiken
2001-01-30 21:00 ` David Woodhouse
2001-01-29 22:08 ` Pavel Machek
2001-01-29 22:31 ` Roger Larsson
2001-01-29 23:46 ` Joe deBlaquiere
2001-01-30 15:08 ` David Woodhouse
2001-01-12 13:21 ` Andrew Morton
2001-01-13 2:45 ` Jay Ts
2001-01-21 0:10 ` yodaiken
2001-01-26 9:14 ` Pavel Machek
2001-01-13 18:11 ` video drivers hog pci bus ? [was:[linux-audio-dev] low-latency scheduling patch for 2.4.0] Jörn Nettingsmeier
2001-01-14 11:35 ` low-latency scheduling patch for 2.4.0 Andrew Morton
2001-01-14 14:38 ` Gregory Maxwell
2001-01-15 10:59 ` Andrew Morton
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=3A77C502.4010504@mvista.com \
--to=george@mvista.com \
--cc=andrewm@uow.edu.au \
--cc=dwmw2@infradead.org \
--cc=jadb@redhat.com \
--cc=linux-audio-dev@ginette.musique.umontreal.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nrg.org \
--cc=yodaiken@fsmlabs.com \
/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