All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: Willy Tarreau <w@1wt.eu>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	akpm@linux-foundation.org
Subject: Re: 2.6.21-rc3-mm1 RSDL results
Date: Fri, 9 Mar 2007 19:10:34 -0600	[thread overview]
Message-ID: <20070310011034.GO10394@waste.org> (raw)
In-Reply-To: <200703101202.25814.kernel@kolivas.org>

On Sat, Mar 10, 2007 at 12:02:25PM +1100, Con Kolivas wrote:
> On Saturday 10 March 2007 09:12, Con Kolivas wrote:
> > On Saturday 10 March 2007 08:57, Willy Tarreau wrote:
> > > On Fri, Mar 09, 2007 at 03:39:59PM -0600, Matt Mackall wrote:
> > > > On Sat, Mar 10, 2007 at 08:19:18AM +1100, Con Kolivas wrote:
> > > > > On Saturday 10 March 2007 08:07, Con Kolivas wrote:
> > > > > > On Saturday 10 March 2007 07:46, Matt Mackall wrote:
> 
> > > > 5x memload: good
> > > > 5x execload: good
> > > > 5x forkload: good
> > > > 5 parallel makes: mostly good
> > > > make -j 5: bad
> > > >
> > > > So what's different between makes in parallel and make -j 5? Make's
> > > > job server uses pipe I/O to control how many jobs are running.
> > >
> > > Matt, could you check with plain 2.6.20 + Con's patch ? It is possible
> > > that he added bugs when porting to -mm, or that someting in -mm causes
> > > the trouble. Your experience with -mm seems so much different from mine
> > > with mainline, there must be a difference somewhere !
> >
> > Good idea.
> 
> It's all very odd Matt. It really isn't behaving anything like you describe 
> for myself or others. It sounds more like a real bug than what the design 
> would do at all. The only things that are different on yours is Beryl and a 
> different graphics card. When you're comparing to mainline are you 
> comparing -mm1 to -mm2 to ensure something else from -mm isn't responsible? 
> Also have you tried rsdl on 2.6.20 as Willy suggested?

Haven't tried -mm2. So far I've tried 2.6.21-rc2-mm2 (aka 'stock'),
2.6.21-rc3-mm1, and 2.6.20+rsdl.

I also did a test with Metacity and saw the same issues under load. So
I think Beryl is not part of the problem.

Right now it's looking like the problem is caused by ccache. Disabling
ccache with 2.6.21-rc2-mm1+tickfix+noyield lets me run make -j 5
acceptably. So my new column would be:

            RSDL+NO_HZ+tickfix+noyield+noccache
make -j 5
 beryl      ok/good
 galeon     ok/good
 mp3        good
 terminal   good
 mouse      good

So it's about on par with 2.6.20, maybe slightly better.

I suspect ccache lock contention is somehow involved though it doesn't
explain why my 5 independent makes test beats out make -j 5.

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2007-03-10  1:23 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 [this message]
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
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=20070310011034.GO10394@waste.org \
    --to=mpm@selenic.com \
    --cc=akpm@linux-foundation.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w@1wt.eu \
    /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.