From: Arjan van de Ven <arjanv@redhat.com>
To: Timothy Miller <miller@techsource.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Dumb question about Voluntary Kernel Preemption Patch
Date: Thu, 15 Jul 2004 21:53:08 +0200 [thread overview]
Message-ID: <1089921188.2710.31.camel@laptop.fenrus.com> (raw)
In-Reply-To: <40F6E504.1@techsource.com>
[-- Attachment #1: Type: text/plain, Size: 415 bytes --]
> 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)?
they only reschedule when there is a higher priority task is waiting to
be run. In all other cases the current code just keeps running.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-07-15 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 20:11 Timothy Miller
2004-07-15 19:53 ` Arjan van de Ven [this message]
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=1089921188.2710.31.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.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
all inboxes | Powered by JetHome®