From: Robert Love <rml@tech9.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: Marc-Christian Petersen <m.c.p@wolk-project.de>,
linux-kernel@vger.kernel.org
Subject: Re: O(1) Scheduler from Ingo vs. O(1) Scheduler from Robert
Date: 04 Oct 2002 15:28:37 -0400 [thread overview]
Message-ID: <1033759718.1247.96.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.44.0210041726350.3806-100000@localhost.localdomain>
On Fri, 2002-10-04 at 11:28, Ingo Molnar wrote:
> On 4 Oct 2002, Robert Love wrote:
>
> > There should _not_ be other things in the patch aside from the
> > scheduler. [...]
>
> hm, i remember there was some 'set max RT priority in .config' stuff
> in it, isnt that the case anymore?
Oh, yes, indeed. I forgot about that.
Since we cleaned up the whole MAX_PRIO thing the only main difference in
my tree is that fact it is exported as a CONFIG setting (and the logic
to implement a new ffs if BITMAP_SIZE changes).
Otherwise the trees aim to be in-sync.
Robert Love
prev parent reply other threads:[~2002-10-04 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 13:33 O(1) Scheduler from Ingo vs. O(1) Scheduler from Robert Marc-Christian Petersen
2002-10-04 15:17 ` Ingo Molnar
2002-10-04 15:15 ` Robert Love
2002-10-04 15:28 ` Ingo Molnar
2002-10-04 19:28 ` Robert Love [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=1033759718.1247.96.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--cc=mingo@elte.hu \
/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