From: Michael Wang <wangyun@linux.vnet.ibm.com>
To: Mike Galbraith <bitbucket@online.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>, 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 v2] sched: wake-affine throttle
Date: Tue, 28 May 2013 16:56:06 +0800 [thread overview]
Message-ID: <51A47126.7070501@linux.vnet.ibm.com> (raw)
In-Reply-To: <1369730970.5857.132.camel@marge.simpson.net>
On 05/28/2013 04:49 PM, Mike Galbraith wrote:
> On Tue, 2013-05-28 at 15:22 +0800, Michael Wang wrote:
>> On 05/28/2013 02:29 PM, Mike Galbraith wrote:
>>> On Tue, 2013-05-28 at 13:02 +0800, Michael Wang wrote:
>>>> On 05/22/2013 10:55 PM, Mike Galbraith wrote:
>>>>> On Wed, 2013-05-22 at 17:25 +0800, Michael Wang wrote:
>>>>>
>>>>>> I've not test the hackbench with wakeup-buddy before, will do it this
>>>>>> time, I suppose the 15% illegal income will suffered, anyway, it's
>>>>>> illegal :)
>>>>>
>>>>> On a 4 socket 40 core (+SMT) box, hackbench wasn't too happy.
>>>>
>>>> I've done more test and now I got the reason of regression...
>>>>
>>>> The writer and reader in hackbench is N:N, prev writer will write all
>>>> the fd then switch to next writer and repeat the same work, so it's
>>>> impossible to setup the buddy relationship by just record the last one,
>>>> and we have to record all the waker/wakee in history, but that means
>>>> unacceptable memory overhead...
>>>
>>> Yeah, that's why I was thinking we'd need a dinky/fast as hell FIFO of
>>> tokens or such to bind waker/wakee more or less reliably. Making such a
>>> scheme cheap enough could be hard.
>>>
>>>> So this buddy idea seems to be bad...
>>>>
>>>> I think a better way may should be allowing pull in most time, but
>>>> filter the very bad cases carefully.
>>>
>>> Any way that is cheap, and fairly accurately recognizes when we're being
>>> stupid will help. First and foremost, it has to be dirt cheap :)
>>>
>>>> For workload like pgbench, we actually just need to avoid pull if that
>>>> will damage the 'mother' thread, which is busy and be relied by many
>>>> 'child'.
>>>
>>> Yeah, 'mom' is the key player. If we can cheaply recognize mom, that
>>> should get us a generic improvement. Not as good as being able to
>>> recognize the size of her+brood as size changes, but better anyway.
>>
>> That's right, I'm trying to rely on the frequency of a task switching
>> it's wakee in the new idea, it's really cheap and somewhat reliable, I
>> appreciate if you could pay an eye on the new patch and let me know you
>> opinion :)
>
> I'll feed it to my 40 core box, hopefully soon.
Thanks for that, wish it taste delicious ;-)
Regards,
Michael Wang
>
> -Mike
>
prev parent reply other threads:[~2013-05-28 8:56 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
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 [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=51A47126.7070501@linux.vnet.ibm.com \
--to=wangyun@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@intel.com \
--cc=bitbucket@online.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 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).