From: Ingo Molnar <mingo@elte.hu>
To: Nick Piggin <npiggin@suse.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Mike Galbraith <efault@gmx.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: newidle balancing in NUMA domain?
Date: Tue, 24 Nov 2009 10:16:30 +0100 [thread overview]
Message-ID: <20091124091630.GH21991@elte.hu> (raw)
In-Reply-To: <20091124065910.GE20981@wotan.suse.de>
* Nick Piggin <npiggin@suse.de> wrote:
> On Mon, Nov 23, 2009 at 06:04:45PM +0100, Ingo Molnar wrote:
> >
> > * Nick Piggin <npiggin@suse.de> wrote:
> >
> > > > .32 is kind of closed, with us being at -rc8.
> > >
> > > It's a bad regression though.
> >
> > It's about 3 months too late for that. Ideally we want performance
>
> Too late for what? Reporting and reverting a regression?
Yes, the revert would be too intrusive so late in the release cycle,
sorry. For such types of scheduler reverts we rarely go beyond -rc5 -
the risks of breaking something are too big.
Note that we have queued up a fix for that about two weeks ago for
v2.6.33 - that fix could be forwarded to stable@kernel.org for 2.6.32.1
merging.
> [...] I don't think so. It is not my problem if patches aren't tested
> well enough before being merged.
There's certainly a wide performance testing being done for scheduler
relevant workloads all the time. If you dont like the end result you are
welcome to help out testing and fixing things (and certainly both).
I'd also welcome help from you to extend 'perf bench sched' with new
testcases. (it has only two so far - the tool just got started so
there's lots of low hanging fruits.) 'perf bench sched numa-cost' would
certainly be usefulful to have.
Thanks,
Ingo
prev parent reply other threads:[~2009-11-24 9:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 11:22 newidle balancing in NUMA domain? Nick Piggin
2009-11-23 11:36 ` Peter Zijlstra
2009-11-23 11:43 ` Nick Piggin
2009-11-23 11:50 ` Peter Zijlstra
2009-11-23 12:16 ` Nick Piggin
2009-11-23 11:45 ` Ingo Molnar
2009-11-23 12:01 ` Nick Piggin
2009-11-23 12:08 ` Ingo Molnar
2009-11-23 12:27 ` Nick Piggin
2009-11-23 12:46 ` Ingo Molnar
2009-11-24 6:36 ` Nick Piggin
2009-11-24 17:24 ` Jason Garrett-Glaser
2009-11-24 18:09 ` Mike Galbraith
2009-11-30 8:19 ` Nick Piggin
2009-12-01 8:18 ` Jason Garrett-Glaser
2009-11-23 14:37 ` Mike Galbraith
2009-11-23 15:11 ` Nick Piggin
2009-11-23 15:21 ` Peter Zijlstra
2009-11-23 15:29 ` Nick Piggin
2009-11-23 15:37 ` Peter Zijlstra
2009-11-24 6:54 ` Nick Piggin
2009-11-23 15:53 ` Mike Galbraith
2009-11-24 6:53 ` Nick Piggin
2009-11-24 8:40 ` Mike Galbraith
2009-11-24 8:58 ` Mike Galbraith
2009-11-24 9:11 ` Ingo Molnar
2009-11-30 8:27 ` Nick Piggin
2009-11-23 17:04 ` Ingo Molnar
2009-11-24 6:59 ` Nick Piggin
2009-11-24 9:16 ` Ingo Molnar [this message]
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=20091124091630.GH21991@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=peterz@infradead.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