From: Nick Piggin <piggin@cyberone.com.au>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Ian Kumlien <pomac@vapor.com>, linux-kernel@vger.kernel.org
Subject: Re: [SHED] Questions.
Date: Sun, 31 Aug 2003 20:46:13 +1000 [thread overview]
Message-ID: <3F51D1F5.8060607@cyberone.com.au> (raw)
In-Reply-To: <3F51D0BD.8030307@cyberone.com.au>
Nick Piggin wrote:
>
>
> Ian Kumlien wrote:
>
>
>>
>> And is the preempt min quantum in there?
>>
>
> No. If you do that, you'll either break the priority concept very
> badly, or you'll break it a little bit and turn the scheduler into
> an O(n) one.
Well I guess you could just break it a little bit without it being O(n)
next prev parent reply other threads:[~2003-08-31 10:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 10:07 [SHED] Questions Ian Kumlien
2003-08-31 10:17 ` Nick Piggin
2003-08-31 10:24 ` Ian Kumlien
2003-08-31 10:41 ` Nick Piggin
2003-08-31 10:46 ` Nick Piggin [this message]
[not found] ` <1062326980.9959.65.camel@big.pomac.com>
[not found] ` <3F51D4A4.4090501@cyberone.com.au>
2003-08-31 11:08 ` Ian Kumlien
2003-08-31 11:31 ` Nick Piggin
2003-08-31 11:43 ` Ian Kumlien
2003-08-31 18:53 ` Robert Love
2003-08-31 19:31 ` Ian Kumlien
2003-08-31 19:51 ` Robert Love
2003-08-31 22:41 ` Ian Kumlien
2003-08-31 23:41 ` Robert Love
2003-09-01 0:00 ` Ian Kumlien
2003-09-01 2:50 ` Con Kolivas
2003-09-01 15:58 ` Antonio Vargas
2003-09-01 22:19 ` Ian Kumlien
2003-09-01 4:03 ` Robert Love
2003-09-01 5:07 ` Con Kolivas
2003-09-01 5:55 ` Robert Love
2003-09-01 22:24 ` Ian Kumlien
2003-09-01 14:21 ` Antonio Vargas
2003-09-01 19:36 ` Geert Uytterhoeven
2003-09-01 22:49 ` Ian Kumlien
2003-09-01 15:07 ` Daniel Phillips
2003-09-01 14:16 ` Antonio Vargas
2003-09-01 23:03 ` Ian Kumlien
2003-09-02 0:04 ` Nick Piggin
2003-09-02 0:23 ` Con Kolivas
2003-09-02 10:25 ` Ian Kumlien
2003-09-02 11:08 ` Nick Piggin
2003-09-02 17:22 ` Ian Kumlien
2003-09-02 23:49 ` Nick Piggin
2003-09-03 23:02 ` Ian Kumlien
2003-09-04 1:39 ` Mike Fedyk
2003-09-02 10:44 ` Wes Janzen
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=3F51D1F5.8060607@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pomac@vapor.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;
as well as URLs for NNTP newsgroup(s).