From: Prakash Punnoor <prakashp@arcor.de>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] nicksched for 2.6.11
Date: Sat, 05 Mar 2005 12:51:13 +0100 [thread overview]
Message-ID: <42299D31.7020901@arcor.de> (raw)
In-Reply-To: <4225A020.5060001@yahoo.com.au>
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
Nick Piggin schrieb:
> I've had a few queries about this, so by "popular" demand, I've
> put my latest nicksched stuff here:
>
> www.kerneltrap.org/~npiggin/2.6.11-nicksched.gz
>
> It includes all the multiprocessor stuff that's in -mm, and also
> my alternate scheduler policy.
Hi,
just to make sure, is it still advised to renice X when using your scheduler?
--
Prakash Punnoor
formerly known as Prakash K. Cheemplavam
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-05 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 11:14 [patch] nicksched for 2.6.11 Nick Piggin
2005-03-05 11:51 ` Prakash Punnoor [this message]
2005-03-07 6:02 ` Nick Piggin
2005-03-07 13:45 ` Felipe Alfaro Solana
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=42299D31.7020901@arcor.de \
--to=prakashp@arcor.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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