All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
Subject: Re: [PATCH] V-5.0.1 Single Priority Array O(1) CPU Scheduler Evaluation
Date: Thu, 26 Aug 2004 10:18:37 +1000	[thread overview]
Message-ID: <412D2C5D.4070206@bigpond.net.au> (raw)
In-Reply-To: <412C789D.2050303@gmx.de>

Prakash K. Cheemplavam wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Peter Williams wrote:
> | Now available for 2.6.9-rc1:
> |
> | ZAPHOD:
> |
> <http://prdownloads.sourceforge.net/cpuse/patch-2.6.9-rc1-spa_zaphod_FULL-v5.0.1?download> 
> 
> 
> |
> |
> | HYDRA:
> |
> <http://prdownloads.sourceforge.net/cpuse/patch-2.6.9-rc1-spa_hydra_FULL-v5.0.1?download> 
> 
> 
> |
> |
> | Others at <https://sourceforge.net/projects/cpuse/>
> |
> | Peter
> 
> Hie, could you provide me link which explans in detail, but yet easy to
> read, how those schedulers work?

Unfortunately, no documentation is available yet.  I've replied 
separately (because of its size) with a description of the schedulers 
and will use that reply as a basis for some on line documentation.  In 
the meanwhile if others are interested I can send them a copy of the 
description.

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

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


  reply	other threads:[~2004-08-26  0:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24  2:46 [PATCH] V-5.0.1 Single Priority Array O(1) CPU Scheduler Evaluation Peter Williams
2004-08-25  8:54 ` Peter Williams
2004-08-25 11:31   ` Prakash K. Cheemplavam
2004-08-26  0:18     ` Peter Williams [this message]
2004-08-26  8:26       ` Prakash K. Cheemplavam

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=412D2C5D.4070206@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prakashkc@gmx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.