public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 11:15:09 -0400	[thread overview]
Message-ID: <1033744512.909.73.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.44.0210041716330.3477-100000@localhost.localdomain>

On Fri, 2002-10-04 at 11:17, Ingo Molnar wrote:

> On Fri, 4 Oct 2002, Marc-Christian Petersen wrote:
> 
> > say, can anyone explain me why $subject patches are so different? What
> > exactly are the important differences, what patch should we use?
> 
> well as far as i can tell Robert has put other stuff into his patch, which
> isnt really part of the O(1) scheduler. So i'd call it "the O(1) scheduler
> plus stuff".

There should _not_ be other things in the patch aside from the
scheduler.  Those patches are based on Ingo's original 2.4 patches with
back-ported fixes from 2.4-ac and 2.5.  Unfortunately, at the moment the
patch is a bit out of sync.  The only 2.4 version of the scheduler I
have been able to keep up-to-date is 2.4-ac... but the patch is not too
bad.

I think the reason my patches differ from Ingo's is that Ingo includes
code that is not yet in mainline 2.5.  For example, last I checked his
patches had the SCHED_BATCH stuff, which is good, but I only want to put
code that is in 2.5 already and tested.

	Robert Love


  reply	other threads:[~2002-10-04 15:10 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 [this message]
2002-10-04 15:28     ` Ingo Molnar
2002-10-04 19:28       ` Robert Love

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=1033744512.909.73.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