From: Nick Piggin <piggin@cyberone.com.au>
To: "Markus Hästbacka" <midian@ihme.org>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Nick's scheduler v19a
Date: Fri, 21 Nov 2003 10:34:06 +1100 [thread overview]
Message-ID: <3FBD4F6E.3030906@cyberone.com.au> (raw)
In-Reply-To: <1069361130.13479.12.camel@midux>
Markus Hästbacka wrote:
>Hi nick! here's some feedback.
>This one day last week, I thougt I could test your scheduler patch.
>I noticed something really good with it. My X had really fast startup.
>everything worked really fast. Even games worked much better than any in
>kernel before (I've tested all from 2.5.74).
>
>So I hope you'll port this patch for test10> if this one wont patch
>clearly.
>
Hi Markus,
Thanks for testing. That sounds quite remarkable, is it possible that
some other change has made the difference? What kernel version did
you patch against, and did you try that same kernel and .config without
my patch? Anyway, I'm glad you're having good results.
Yes, this one will probably apply to test10 should it ever apper. If not
I will port it.
Nick
next prev parent reply other threads:[~2003-11-20 23:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-15 13:11 Nick's scheduler v19a Nick Piggin
2003-11-20 20:45 ` Markus Hästbacka
2003-11-20 23:34 ` Nick Piggin [this message]
2003-11-21 6:11 ` Markus Hästbacka
2003-11-21 6:20 ` Nick Piggin
2003-11-21 9:06 ` Markus Hästbacka
2003-11-21 9:14 ` Nick Piggin
2003-11-21 9:32 ` Markus Hästbacka
2003-11-21 9:54 ` Måns Rullgård
2003-11-21 10:21 ` Markus Hästbacka
2003-11-21 16:19 ` Timothy Miller
2003-11-21 17:00 ` Markus Hästbacka
2003-11-24 7:45 ` Peter C. Ndikuwera
2004-01-12 19:40 ` Bug found (Was: Re: Nick's scheduler v19a) Markus Hästbacka
2003-12-03 16:14 ` Nick's scheduler v19a Markus Hästbacka
2003-12-03 22:15 ` Nick Piggin
2003-12-07 21:52 ` Markus Hästbacka
2003-12-07 23:05 ` Nick Piggin
[not found] <3FF79C54.4070200@cyberone.com.au>
2004-02-02 11:21 ` Markus Hästbacka
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=3FBD4F6E.3030906@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=midian@ihme.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