From: Bill Davidsen <davidsen@tmr.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Variable ticks
Date: Mon, 25 Jul 2005 14:59:49 -0400 [thread overview]
Message-ID: <42E536A5.8060007@tmr.com> (raw)
I was thinking about variable tick times, and I can think of three
classes of action needing CPU attention.
- device interrupts, which occur at no predictable time but would pull
the CPU out of a HLT or low power state.
- process sleeps of various kinds, which have a known time of occurence.
- polled devices...
Question one, are there other actions to consider?
Question two, what about those polled devices?
I've been asked to give a high level overview of the recent discussion
for a meeting, and while I want to keep it at the level of "slower
clock, fewer interrupts" and "faster clock, better sleep resolution," I
don't want to leave out any important issues, or be asked a question
(like how to handle polling devices) when I have no idea what people are
thinking in an area.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next reply other threads:[~2005-07-25 18:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 18:59 Bill Davidsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-25 19:10 Variable ticks Brown, Len
2005-07-25 21:05 ` Bill Davidsen
2005-07-25 21:19 Brown, Len
2005-07-25 21:25 ` Lee Revell
2005-07-27 8:13 ` Zwane Mwaikambo
2005-07-27 20:43 ` Lee Revell
2005-07-27 21:06 ` Valdis.Kletnieks
2005-07-27 22:03 ` Zwane Mwaikambo
2005-07-26 15:50 ` Bill Davidsen
2005-07-26 16:08 Brown, Len
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=42E536A5.8060007@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox