public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Markus Hästbacka" <midian@ihme.org>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Nick's scheduler v19a
Date: Fri, 21 Nov 2003 08:11:42 +0200	[thread overview]
Message-ID: <1069395102.16807.11.camel@midux> (raw)
In-Reply-To: <3FBD4F6E.3030906@cyberone.com.au>

[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]

Hi nick.
it seems that this patch changed everything, I patched against
2.6.0-test9-bk19. I didn't upgrade any software before I booted to your
patch. and I tested the 2.6.0-test9-bk22 without the patch it worked
just as all other kernels without the patch. I've had the same .config
from test3 (maybe some small changes if new drivers appeared).

I can't say that 2.6 performance is bad, it's better than 2.4, but now
this is even better. 

So now I'm booted back to your patch and I like this difference in X
performance, I can't ask for more. :)

Regards,

Markus
On Fri, 2003-11-21 at 01:34, Nick Piggin wrote:
> 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
-- 
"Software is like sex, it's better when it's free."
Markus Hästbacka <midian at ihme.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-11-21  6:11 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
2003-11-21  6:11     ` Markus Hästbacka [this message]
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=1069395102.16807.11.camel@midux \
    --to=midian@ihme.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.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