From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: a.p.zijlstra@chello.nl, mingo@elte.hu, vatsa@in.ibm.com,
dmitry.adamushko@gmail.com, efault@gmx.de,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH 1/2] sched: higher granularity load on 64bit systems
Date: Thu, 24 Apr 2008 07:28:14 +0530 [thread overview]
Message-ID: <20080424015814.GA17190@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080423.172710.152976766.davem@davemloft.net>
On Wed, Apr 23, 2008 at 05:27:10PM -0700, David Miller wrote:
> From: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Date: Thu, 24 Apr 2008 00:07:56 +0200
>
> > The below is an RFC because for some reason it regresses kbuild by 5% on
> > my machine (and more on the largesmp that are the reason for it).
>
> This causes my 64-cpu Niagara2 box to completely hang when I run "make
> clean" on a kernel tree after a fresh bootup.
>
Any traces? Or anything? It stayed pretty stable on the 128 way I trying
on, (but for the performance regression) and I was able to reproduce
your group scheduler hang (or so i think, it might a separate one
altogether.)
> Can we just revert all of this broken code until it's sorted out? :-/
>
> We're going on 4 days with unfixed major regressions from the
> scheduler tree merge, and these regressions make systems unusable.
>
> This is blocking my own work, and I'm starting to lose my patience.
--
regards,
Dhaval
next prev parent reply other threads:[~2008-04-24 1:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 22:07 [RFC][PATCH 1/2] sched: higher granularity load on 64bit systems Peter Zijlstra
2008-04-23 22:09 ` [RFC][PATCH 2/2] sched: aggregate_group_shares no loop Peter Zijlstra
2008-04-24 0:27 ` [RFC][PATCH 1/2] sched: higher granularity load on 64bit systems David Miller
2008-04-24 1:58 ` Dhaval Giani [this message]
2008-04-24 2:13 ` David Miller
2008-04-24 6:47 ` Peter Zijlstra
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=20080424015814.GA17190@linux.vnet.ibm.com \
--to=dhaval@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=davem@davemloft.net \
--cc=dmitry.adamushko@gmail.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vatsa@in.ibm.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 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.