public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Mark Lord <lkml@rtr.ca>
Cc: Serge Belyshev <belyshev@depni.sinp.msu.ru>,
	William Lee Irwin III <wli@holomorphy.com>,
	Matt Mackall <mpm@selenic.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	akpm@linux-foundation.org
Subject: Re: 2.6.21-rc3-mm1 RSDL results
Date: Sun, 11 Mar 2007 10:38:59 +1100	[thread overview]
Message-ID: <200703111038.59387.kernel@kolivas.org> (raw)
In-Reply-To: <200703111034.02159.kernel@kolivas.org>

On Sunday 11 March 2007 10:34, Con Kolivas wrote:
> On Sunday 11 March 2007 05:21, Mark Lord wrote:
> > Con Kolivas wrote:
> > > On Saturday 10 March 2007 05:07, Mark Lord wrote:
> > >> Mmm.. when it's good, it's *really* good.
> > >> My desktop feels snappier and all of that.
> > >
> > >..
> > >
> > >> But when it's bad, it stinks.
> > >> Like when a "make -j2" kernel rebuild is happening in a background
> > >> window
> > >
> > > And that's bad. When you say "it stinks" is it more than 3 times
> > > slower? It should be precisely 3 times slower under that load (although
> > > low cpu using things like audio wont be affected by running 3 times
> > > slower). If it feels like much more than that much slower, there is a
> > > bug there somewhere.
> >
> > Scrolling windows is incredibly jerkey, and very very sluggish
> > when images are involved (eg. a large web page in firefox).
> >
> > > As another reader suggested, how does it run with the compile 'niced'?
> > > How does it perform with make (without a -j number).
> >
> > Yes, it behaves itself when the "make -j2" is nice'd.
> >
> > >> This is on a Pentium-M 760 single-core, w/2GB SDRAM (notebook).
> > >
> > > What HZ are you running? Are you running a Beryl desktop?
> >
> > HZ==1000, NO_HZ, Kubunutu Dapper Drake distro, ATI X300 open-source X.org
> > driver.
>
> Can you try the new version of RSDL. Assuming it doesn't oops on you it has
> some accounting bugfixes which may have been biting you.

Oh I just checked the mesa repo for that driver as well. It seems the r300 
drivers have sched_yield in them as well, but not all components. You may be 
getting bitten by this too.

http://webcvs.freedesktop.org/mesa/Mesa/src/mesa/drivers/dri/r300/radeon_ioctl.c?revision=1.14&view=markup

I don't really know what the radeon and other models are so I'm not sure if it 
applies to your hardware; I just did a random search through the r300 
directory.

-- 
-ck

  reply	other threads:[~2007-03-10 23:12 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-09  5:39 2.6.21-rc3-mm1 RSDL results Matt Mackall
2007-03-09  6:28 ` Con Kolivas
2007-03-09  7:53   ` Matt Mackall
2007-03-09  8:20     ` Matt Mackall
2007-03-09  8:39       ` Con Kolivas
2007-03-09 18:27         ` Matt Mackall
2007-03-09 20:15           ` Con Kolivas
2007-03-09 20:26             ` Con Kolivas
2007-03-09 20:51               ` Matt Mackall
2007-03-09 20:55             ` Matt Mackall
2007-03-09 20:46         ` Matt Mackall
2007-03-09 21:07           ` Con Kolivas
2007-03-09 21:19             ` Con Kolivas
2007-03-09 21:39               ` Matt Mackall
2007-03-09 21:57                 ` Con Kolivas
2007-03-09 22:18                   ` Con Kolivas
2007-03-09 22:29                     ` Matt Mackall
2007-03-09 23:02                       ` Con Kolivas
2007-03-09 23:06                         ` Matt Mackall
2007-03-10  0:31                           ` Con Kolivas
2007-03-10  0:34                       ` Con Kolivas
2007-03-10  0:49                         ` Matt Mackall
2007-03-10  1:28                           ` Con Kolivas
2007-03-10  1:42                             ` Matt Mackall
2007-03-10  2:10                               ` Kyle Moffett
2007-03-10  2:20                               ` Con Kolivas
2007-03-10  2:26                                 ` Matt Mackall
2007-03-10  2:53                                   ` Con Kolivas
2007-03-09 21:57                 ` Willy Tarreau
2007-03-09 22:12                   ` Con Kolivas
2007-03-09 22:20                     ` Matt Mackall
2007-03-09 22:31                     ` Willy Tarreau
2007-03-10  1:02                     ` Con Kolivas
2007-03-10  1:10                       ` Matt Mackall
2007-03-10 17:01             ` James Cloos
2007-03-10 23:16               ` Con Kolivas
2007-03-11 12:38                 ` James Cloos
2007-03-11 12:52                   ` Con Kolivas
2007-03-09 21:10           ` Matt Mackall
2007-03-09  8:36     ` Con Kolivas
2007-03-09  9:07       ` Serge Belyshev
2007-03-09  9:49         ` William Lee Irwin III
2007-03-09 10:36           ` Serge Belyshev
2007-03-09 18:07             ` Mark Lord
2007-03-09 18:24               ` Jeffrey Hundstad
2007-03-09 20:23               ` Con Kolivas
2007-03-10 18:21                 ` Mark Lord
2007-03-10 23:34                   ` Con Kolivas
2007-03-10 23:38                     ` Con Kolivas [this message]
2007-03-13 18:21                     ` Mark Lord
2007-03-13 20:26                       ` Con Kolivas
2007-03-13 22:06                         ` Mark Lord

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=200703111038.59387.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=akpm@linux-foundation.org \
    --cc=belyshev@depni.sinp.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=mpm@selenic.com \
    --cc=wli@holomorphy.com \
    /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