All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Goller <dgoller@satx.rr.com>
To: Michael Frank <mflt1@micrologica.com.hk>
Cc: Mike Fedyk <mfedyk@matchmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.21-rc6
Date: 31 May 2003 19:39:12 -0500	[thread overview]
Message-ID: <1054427952.7416.2.camel@schlaefer> (raw)
In-Reply-To: <200305311912.29558.mflt1@micrologica.com.hk>

On Sat, 2003-05-31 at 06:12, Michael Frank wrote:
> On Saturday 31 May 2003 15:06, Daniel Goller wrote:
> > On Fri, 2003-05-30 at 15:52, Mike Fedyk wrote:
> > > On Fri, May 30, 2003 at 02:08:51PM -0500, Daniel Goller 
> wrote:
> > > > i tried 2.4.21-rc6 as i was told it might fix the
> > > > mouse stalling on heavy disk IO problem and i would
> > > > like to report that it DOES fix them for the most
> > > > part, even certain compiles/benchmarks/stress tests
> > > > that could stall my pc for seconds now affect the
> > > > mouse for mere fractions of one second, situations
> > > > that used to cause short stalls are now a thing of
> > > > the past
> > > >
> > > > 2.4.21-rc6 is the best kernel i have tried to date
> > > > and i have tried many on my quest to get a smooth
> > > > mouse
> > >
> > > There are reports that 2.4.18 also "fixed" the problems
> > > with the mouse.  Can you verify?
> >
> 
> Yes, it performs similar to -rc6 but not nearly as good as 
> 2.5.70.
> 
> On 2.5.70 the mouse is really smooth all the time, scrollong 
> of large pages in opera is fairly smooth most the time also 
> with large disk io loads such as the script i posted 
> earlier.
> 
> Regards
> Michael
> 

unfortunately the radeon dri is broken in 2.5.70 so i havent tried that
much, need to see if someone already suggests a fix for this unused int
(it seems unused to me, after a *quick* look through the file) i guess i
will have to subscribe now to lkml



  reply	other threads:[~2003-06-01  0:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 19:08 Linux 2.4.21-rc6 Daniel Goller
2003-05-30 20:52 ` Mike Fedyk
2003-05-31  7:06   ` Daniel Goller
2003-05-31 11:12     ` Michael Frank
2003-06-01  0:39       ` Daniel Goller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-29  0:55 Marcelo Tosatti
2003-05-29  1:22 ` Con Kolivas
2003-05-29  5:24   ` Marc Wilson
2003-05-29  5:34     ` Riley Williams
2003-05-29  5:57       ` Marc Wilson
2003-05-29  7:15         ` Riley Williams
2003-05-29  8:38         ` Willy Tarreau
2003-05-29  8:40           ` Willy Tarreau
2003-06-03 16:02         ` Marcelo Tosatti
2003-06-03 16:13           ` Marc-Christian Petersen
2003-06-04 21:54             ` Pavel Machek
2003-06-05  2:10               ` Michael Frank
2003-06-03 16:30           ` Michael Frank
2003-06-03 16:53             ` Matthias Mueller
2003-06-03 16:59             ` Marc-Christian Petersen
2003-06-03 17:03               ` Marc-Christian Petersen
2003-06-03 18:02                 ` Anders Karlsson
2003-06-03 21:12                   ` J.A. Magallon
2003-06-03 21:18                     ` Marc-Christian Petersen
2003-06-03 17:23               ` Michael Frank
2003-06-04 14:56             ` Jakob Oestergaard
2003-06-04  4:04           ` Marc Wilson
2003-05-29 10:02 ` Con Kolivas
2003-05-29 18:00 ` Georg Nikodym

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=1054427952.7416.2.camel@schlaefer \
    --to=dgoller@satx.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.com \
    --cc=mflt1@micrologica.com.hk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.