From: Michael Wang <wangyun@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>, Mike Galbraith <efault@gmx.de>,
Alex Shi <alex.shi@intel.com>, Namhyung Kim <namhyung@kernel.org>,
Paul Turner <pjt@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Nikunj A. Dadhania" <nikunj@linux.vnet.ibm.com>,
Ram Pai <linuxram@us.ibm.com>
Subject: Re: [PATCH] sched: wake-affine throttle
Date: Fri, 12 Apr 2013 11:17:04 +0800 [thread overview]
Message-ID: <51677CB0.606@linux.vnet.ibm.com> (raw)
In-Reply-To: <1365583873.30071.31.camel@laptop>
On 04/10/2013 04:51 PM, Peter Zijlstra wrote:
> On Wed, 2013-04-10 at 11:30 +0800, Michael Wang wrote:
>> | 15 GB | 32 | 35918 | | 37632 | +4.77% | 47923 | +33.42% |
>> 52241 | +45.45%
>
> So I don't get this... is wake_affine() once every milisecond _that_
> expensive?
>
> Seeing we get a 45%!! improvement out of once every 100ms that would
> mean we're like spending 1/3rd of our time in wake_affine()? that's
> preposterous. So what's happening?
Hi, Peter
I think Mike has very well explained the reason why throttle bring us
benefit and why the benefit looks so significant when interval get
higher, could you please take a look at his mail and see whether it
addressed this concern?
And thanks Mike again for the excellent analysis :)
Regards,
Michael Wang
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2013-04-12 3:17 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 3:30 [PATCH] sched: wake-affine throttle Michael Wang
2013-04-10 4:16 ` Alex Shi
2013-04-10 5:11 ` Michael Wang
2013-04-10 5:27 ` Alex Shi
2013-04-10 8:51 ` Peter Zijlstra
2013-04-10 9:22 ` Michael Wang
2013-04-11 6:01 ` Michael Wang
2013-04-11 7:30 ` Mike Galbraith
2013-04-11 8:26 ` Michael Wang
2013-04-11 8:44 ` Mike Galbraith
2013-04-11 9:00 ` Mike Galbraith
2013-04-11 9:02 ` Michael Wang
2013-04-12 3:17 ` Michael Wang [this message]
2013-04-22 4:21 ` Michael Wang
2013-04-22 5:27 ` Mike Galbraith
2013-04-22 6:19 ` Michael Wang
2013-04-22 10:23 ` Peter Zijlstra
2013-04-22 10:35 ` Ingo Molnar
2013-04-23 4:05 ` Michael Wang
2013-04-22 17:49 ` Paul Turner
2013-04-23 4:01 ` Michael Wang
2013-04-27 2:46 ` Michael Wang
2013-05-02 5:48 ` Michael Wang
2013-05-02 7:10 ` Mike Galbraith
2013-05-02 7:36 ` Michael Wang
2013-05-03 3:46 ` Michael Wang
2013-05-03 5:01 ` Mike Galbraith
2013-05-03 5:57 ` Michael Wang
2013-05-03 6:14 ` Mike Galbraith
2013-05-04 2:20 ` Michael Wang
2013-05-07 2:46 ` Michael Wang
2013-05-13 2:27 ` Michael Wang
2013-05-16 7:40 ` Michael Wang
2013-05-16 7:45 ` Michael Wang
2013-05-21 3:20 ` [PATCH v2] " Michael Wang
2013-05-21 6:47 ` Alex Shi
2013-05-21 6:52 ` Michael Wang
2013-05-22 8:49 ` Peter Zijlstra
2013-05-22 9:25 ` Michael Wang
2013-05-22 14:55 ` Mike Galbraith
2013-05-23 2:12 ` Michael Wang
2013-05-28 5:02 ` Michael Wang
2013-05-28 6:29 ` Mike Galbraith
2013-05-28 7:22 ` Michael Wang
2013-05-28 8:49 ` Mike Galbraith
2013-05-28 8:56 ` Michael Wang
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=51677CB0.606@linux.vnet.ibm.com \
--to=wangyun@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@intel.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=nikunj@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.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.