public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Terrible interactivity with 2.6.0-t9-mm3
Date: Sun, 16 Nov 2003 21:24:25 +0100	[thread overview]
Message-ID: <3FB7DCF9.5090205@gmx.de> (raw)
In-Reply-To: <20031116192643.GB15439@zip.com.au>

CaT wrote:

 > I just noticed major interactivity problems whilst ogging one of my

[...]

 > Doh. :/ This is the first time this has been so bad that I've felt
 > it was worth writing about. :/


Yup, I was using a patched mm3 so I wanted to try the plain one, but due 
to your post, I can conclude it really is mm3 which is really bad. I 
noticed this as well. Using Nick's CPU scheduler things are not thaaat 
bad, but still far from mm2. I think there is some major problem 
introduced to mm3. Without Nicks patch doing an emerge/compiling, even 
my mouse heavily stutters like hell, regradless of the used io 
scheduler. With Nick's patch the mouse is rather OK, but the rest if the 
system is still not really usable. It is not a HD problem...

Going back to mm2 (patched mm2) and everything it fine again.

Athlon XP 1900MHz
1GB DDR RAM
NFORCE2 Chipset

Prakash



  reply	other threads:[~2003-11-16 20:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-16 19:26 Terrible interactivity with 2.6.0-t9-mm3 CaT
2003-11-16 20:24 ` Prakash K. Cheemplavam [this message]
2003-11-16 21:42   ` Andrew Morton
2003-11-16 22:06     ` Arnaldo Carvalho de Melo
2003-11-16 22:13       ` Andrew Morton
2003-11-16 22:18         ` CaT
2003-11-17  0:16     ` Panagiotis Papadakos
2003-11-17  2:20     ` Gawain Lynch
2003-11-17  2:49       ` Andrew Morton
2003-11-17  3:11         ` Gawain Lynch
2003-11-17  3:54         ` Gene Heskett
2003-11-17  4:19           ` Nick Piggin
2003-11-17  4:47             ` Gene Heskett
2003-11-17  5:17               ` Nick Piggin
  -- strict thread matches above, loose matches on Subject: below --
2003-11-17 12:11 Ronny V. Vindenes
2003-11-17 13:12 ` Prakash K. Cheemplavam
2003-11-17 19:46   ` Thomas Schlichter
2003-11-17 21:27     ` john stultz
2003-11-17 22:44       ` john stultz
2003-11-17 22:51       ` Prakash K. Cheemplavam
2003-11-17 22:55         ` john stultz
2003-11-17 23:04           ` john stultz
2003-11-17 23:46             ` Thomas Schlichter
2003-11-18 13:24             ` Prakash K. Cheemplavam
2003-11-18 16:11               ` Prakash K. Cheemplavam
2003-11-18 18:28                 ` john stultz
2003-11-18 16:15               ` Prakash K. Cheemplavam
2003-11-17 13:15 ` Felipe Alfaro Solana
2003-11-17 19:36 ` Andrew Morton
2003-11-17 19:35   ` john stultz
2003-11-18 18:56   ` Dominik Brodowski
2003-11-18 19:18     ` john stultz

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=3FB7DCF9.5090205@gmx.de \
    --to=prakashpublic@gmx.de \
    --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