From: Jason Low <jason.low2@hp.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v3] sched: Limit idle balance based on max cost per sched domain
Date: Thu, 22 Aug 2013 12:42:10 -0700 [thread overview]
Message-ID: <1377200530.2710.2.camel@j-VirtualBox> (raw)
In-Reply-To: <20130822111027.GJ31370@twins.programming.kicks-ass.net>
On Thu, 2013-08-22 at 13:10 +0200, Peter Zijlstra wrote:
> Fully agreed, this is something we should do regardless -- for as long
> as we preserve the avg_idle() machinery anyway :-)
Okay, I'll have the avg_idle fix as part 1 of the v4 patchset.
> The thing you 'forgot' to mention is if this patch actually helps you
> workload?
Yes, this helps a lot of the workloads on the 8 socket machines. I will
be sure to include some numbers next time.
prev parent reply other threads:[~2013-08-22 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 9:32 [RFC PATCH v3] sched: Limit idle balance based on max cost per sched domain Jason Low
2013-08-22 11:10 ` Peter Zijlstra
2013-08-22 19:42 ` Jason Low [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=1377200530.2710.2.camel@j-VirtualBox \
--to=jason.low2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).