public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Chris Han <xiphux@gmail.com>, Con Kolivas <kernel@kolivas.org>
Subject: Re: [ANNOUNCE][RFC] PlugSched-3.0.2 for 2.6.11
Date: Sat, 12 Mar 2005 17:13:17 +1100	[thread overview]
Message-ID: <4232887D.3090007@bigpond.net.au> (raw)
In-Reply-To: <4226796A.9080502@bigpond.net.au>

Peter Williams wrote:
> A patch of PlugSched-3.0.2 (containing ingosched, staircase, 
> spa_no_frills and zaphod CPU schedulers) against a 2.6.11 kernel is
> available for download from:
> 
> <http://prdownloads.sourceforge.net/cpuse/plugsched-3.0.2-for-2.6.11.patch?download> 
> 
> 
> PlugSched's version number has been bumped to 3.0.2 as it contains minor 
> bug fixes and a patch for this version against a 2.6.10 kernel is 
> available at:
> 
> <http://prdownloads.sourceforge.net/cpuse/plugsched-3.0.2-for-2.6.10.patch?download> 
> 
> 
> and against a CKRM modified 2.6.10 kernel at:
> 
> <http://prdownloads.sourceforge.net/cpuse/plugsched-3.0.2%2Bckrm-E17-for-2.6.10.patch?download> 

A bug fix update, PlugSched-3.0.2.1, of the 2.6.11 version is available at:

<http://prdownloads.sourceforge.net/cpuse/plugsched-3.0.2.1-for-2.6.11.patch?download>

and an incremental patch from 3.0.2 to 3.0.2.1 is available at:

<http://prdownloads.sourceforge.net/cpuse/plugsched-3.0.2-to-3.0.2.1-for-2.6.11.patch?download>

Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce

      reply	other threads:[~2005-03-12  6:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03  2:41 [ANNOUNCE][RFC] PlugSched-3.0.2 for 2.6.11 Peter Williams
2005-03-12  6:13 ` Peter Williams [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=4232887D.3090007@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiphux@gmail.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