From: Peter Zijlstra <peterz@infradead.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Mike Galbraith <efault@gmx.de>,
linux-kernel@vger.kernel.org, linaro-dev@lists.linaro.org,
mingo@redhat.com, Venkatesh Pallipadi <venki@google.com>,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: [RFC] sched: nohz_idle_balance
Date: Thu, 13 Sep 2012 10:45:49 +0200 [thread overview]
Message-ID: <1347525949.15764.109.camel@twins> (raw)
In-Reply-To: <CAKfTPtCoYjiZphPqyYtmEN-jR=hbAUMLbWSkD9BoWRiVkmE=3Q@mail.gmail.com>
On Thu, 2012-09-13 at 10:37 +0200, Vincent Guittot wrote:
> > I think you need to present numbers showing benefit. Crawling all over
> > a mostly idle (4096p?) box is decidedly bad thing to do.
Yeah, but we're already doing that anyway.. we know nohz idle balance
doesn't scale. Venki and Suresh were working on that, but with Venki
switching jobs this work got dropped.
I did talk to Suresh about it a week or so ago.. I think he was going to
look at it again.
next prev parent reply other threads:[~2012-09-13 8:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 4:11 [RFC] sched: nohz_idle_balance Vincent Guittot
2012-09-13 6:49 ` Mike Galbraith
2012-09-13 8:19 ` Peter Zijlstra
2012-09-13 10:29 ` Mike Galbraith
2012-09-13 13:41 ` Rakib Mullick
[not found] ` <CAKfTPtBQ7Y1xGOe9NZw8AhNbOzGgkVMgYyXjVa1d308kdG6bfQ@mail.gmail.com>
[not found] ` <1347521382.6821.61.camel@marge.simpson.net>
[not found] ` <CAKfTPtCvg1qxUv02-dO9qD2HiFzS_bA2Gr0mrN=8LEA3eXA7Bg@mail.gmail.com>
[not found] ` <1347522994.6821.67.camel@marge.simpson.net>
2012-09-13 8:37 ` Vincent Guittot
2012-09-13 8:45 ` Peter Zijlstra [this message]
2012-09-13 8:53 ` Peter Zijlstra
2012-09-13 8:18 ` Peter Zijlstra
2012-09-14 6:12 ` [tip:sched/core] sched: Fix nohz_idle_balance() tip-bot for Vincent Guittot
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=1347525949.15764.109.camel@twins \
--to=peterz@infradead.org \
--cc=efault@gmx.de \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=suresh.b.siddha@intel.com \
--cc=venki@google.com \
--cc=vincent.guittot@linaro.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