From: Timothy Miller <miller@techsource.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Dumb question about Voluntary Kernel Preemption Patch
Date: Thu, 15 Jul 2004 16:11:48 -0400 [thread overview]
Message-ID: <40F6E504.1@techsource.com> (raw)
I sent this before, but I didn't get a response. Either people missed
it or it wasn't worth responding to. I'll give it one more try before I
shut up about it...
I have a question about voluntary kernel preemption in general.
(Shouldn't we call this "cooperative multitasking"?)
There are two disadvantages to voluntary preemption. One is that the
kernel thread my not sleep enough (high latency), and the other is that
the kernel thread may sleep too much (wasted CPU for context switch
overhead). The advantage of using the timer interrupt instead is that
the preemption happens only as often as it needs to.
My question is this: Do your reschedule points (might_sleep or whatever
you end up using) ALWAYS reschedule, or do they only reschedule after a
certain period of time (timer interrupt increments counter, and
reschedule point does nothing if it's too early)?
next reply other threads:[~2004-07-15 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 20:11 Timothy Miller [this message]
2004-07-15 19:53 ` Dumb question about Voluntary Kernel Preemption Patch Arjan van de Ven
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=40F6E504.1@techsource.com \
--to=miller@techsource.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 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.