From: Nick Piggin <piggin@cyberone.com.au>
To: Cliff White <cliffw@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, akpm@osdl.org
Subject: Re: Nick's scheduler policy v15
Date: Sat, 13 Sep 2003 12:06:36 +1000 [thread overview]
Message-ID: <3F627BAC.5040706@cyberone.com.au> (raw)
In-Reply-To: <200309121839.h8CIdao22695@mail.osdl.org>
Cliff White wrote:
>>Hi,
>>http://www.kerneltrap.org/~npiggin/v15/
>>
>>
>
>Here are results for several recent kernels for comparison.
>the sched-rollup-nopolicy tests are still running.
>Performance of v15 suffers as number of CPU's increase.
>At 8 cpu's, delta is noticeable vs stock -test5
>cliffw
>
OK, so it hasn't crashed? Do you have the profiles up?
Thanks,
Nick
next prev parent reply other threads:[~2003-09-13 2:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 14:34 Nick's scheduler policy v15 Nick Piggin
2003-09-11 23:29 ` Cliff White
2003-09-12 4:43 ` Mike Fedyk
2003-09-12 18:05 ` Bill Davidsen
2003-09-12 18:39 ` Cliff White
2003-09-13 2:06 ` Nick Piggin [this message]
2003-09-13 11:17 ` Nick Piggin
2003-09-14 6:25 ` Cliff White
2003-09-22 5:40 ` Nick's scheduler policy v15a Nick Piggin
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=3F627BAC.5040706@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=cliffw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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