From: Michael Wang <wangyun@linux.vnet.ibm.com>
To: Mike Galbraith <bitbucket@online.de>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
peterz@infradead.org, mingo@kernel.org, a.p.zijlstra@chello.nl
Subject: Re: [RFC PATCH 0/2] sched: simplify the select_task_rq_fair()
Date: Mon, 21 Jan 2013 17:22:41 +0800 [thread overview]
Message-ID: <50FD08E1.8000302@linux.vnet.ibm.com> (raw)
In-Reply-To: <1358759355.4994.108.camel@marge.simpson.net>
On 01/21/2013 05:09 PM, Mike Galbraith wrote:
> On Mon, 2013-01-21 at 15:45 +0800, Michael Wang wrote:
>> On 01/21/2013 03:09 PM, Mike Galbraith wrote:
>>> On Mon, 2013-01-21 at 07:42 +0100, Mike Galbraith wrote:
>>>> On Mon, 2013-01-21 at 13:07 +0800, Michael Wang wrote:
>>>
>>>>> May be we could try change this back to the old way later, after the aim
>>>>> 7 test on my server.
>>>>
>>>> Yeah, something funny is going on.
>>>
>>> Never entering balance path kills the collapse. Asking wake_affine()
>>> wrt the pull as before, but allowing us to continue should no idle cpu
>>> be found, still collapsed. So the source of funny behavior is indeed in
>>> balance_path.
>>
>> Below patch based on the patch set could help to avoid enter balance path
>> if affine_sd could be found, just like the old logical, would you like to
>> take a try and see whether it could help fix the collapse?
>
> No, it does not.
Hmm...what have changed now compared to the old logical?
May be I missed some thing, well, I think I need to find a machine which
could reproduce the issue firstly.
Regards,
Michael Wang
>
>>
>> Regards,
>> Michael Wang
>>
>> ---
>> kernel/sched/fair.c | 14 ++++++++------
>> 1 files changed, 8 insertions(+), 6 deletions(-)
>>
>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>> index d600708..4e95bb0 100644
>> --- a/kernel/sched/fair.c
>> +++ b/kernel/sched/fair.c
>> @@ -3297,6 +3297,8 @@ next:
>> sg = sg->next;
>> } while (sg != sd->groups);
>> }
>> +
>> + return -1;
>> done:
>> return target;
>> }
>> @@ -3349,7 +3351,7 @@ select_task_rq_fair(struct task_struct *p, int sd_flag, int wake_flags)
>> * some cases.
>> */
>> new_cpu = select_idle_sibling(p, prev_cpu);
>> - if (idle_cpu(new_cpu))
>> + if (new_cpu != -1)
>> goto unlock;
>>
>> /*
>> @@ -3363,15 +3365,15 @@ select_task_rq_fair(struct task_struct *p, int sd_flag, int wake_flags)
>> goto balance_path;
>>
>> new_cpu = select_idle_sibling(p, cpu);
>> - if (!idle_cpu(new_cpu))
>> - goto balance_path;
>> -
>> /*
>> * Invoke wake_affine() finally since it is no doubt a
>> * performance killer.
>> */
>> - if (wake_affine(sbm->affine_map[prev_cpu], p, sync))
>> - goto unlock;
>> + if (new_cpu == -1 ||
>> + !wake_affine(sbm->affine_map[prev_cpu], p, sync))
>> + new_cpu = prev_cpu;
>> +
>> + goto unlock;
>> }
>>
>> balance_path:
>
>
> --
> 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-01-21 9:22 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1356588535-23251-1-git-send-email-wangyun@linux.vnet.ibm.com>
2013-01-09 9:28 ` [RFC PATCH 0/2] sched: simplify the select_task_rq_fair() Michael Wang
2013-01-12 8:01 ` Mike Galbraith
2013-01-12 10:19 ` Mike Galbraith
2013-01-14 9:21 ` Mike Galbraith
2013-01-15 3:10 ` Michael Wang
2013-01-15 4:52 ` Mike Galbraith
2013-01-15 8:26 ` Michael Wang
2013-01-17 5:55 ` Michael Wang
2013-01-20 4:09 ` Mike Galbraith
2013-01-21 2:50 ` Michael Wang
2013-01-21 4:38 ` Mike Galbraith
2013-01-21 5:07 ` Michael Wang
2013-01-21 6:42 ` Mike Galbraith
2013-01-21 7:09 ` Mike Galbraith
2013-01-21 7:45 ` Michael Wang
2013-01-21 9:09 ` Mike Galbraith
2013-01-21 9:22 ` Michael Wang [this message]
2013-01-21 9:44 ` Mike Galbraith
2013-01-21 10:30 ` Mike Galbraith
2013-01-22 3:43 ` Michael Wang
2013-01-22 8:03 ` Mike Galbraith
2013-01-22 8:56 ` Michael Wang
2013-01-22 11:34 ` Mike Galbraith
2013-01-23 3:01 ` Michael Wang
2013-01-23 5:02 ` Mike Galbraith
2013-01-22 14:41 ` Mike Galbraith
2013-01-23 2:44 ` Michael Wang
2013-01-23 4:31 ` Mike Galbraith
2013-01-23 5:09 ` Michael Wang
2013-01-23 6:28 ` Mike Galbraith
2013-01-23 7:10 ` Michael Wang
2013-01-23 8:20 ` Mike Galbraith
2013-01-23 8:30 ` Michael Wang
2013-01-23 8:49 ` Mike Galbraith
2013-01-23 9:00 ` Michael Wang
2013-01-23 9:18 ` Mike Galbraith
2013-01-23 9:26 ` Michael Wang
2013-01-23 9:37 ` Mike Galbraith
2013-01-23 9:32 ` Mike Galbraith
2013-01-24 6:01 ` Michael Wang
2013-01-24 6:51 ` Mike Galbraith
2013-01-24 7:15 ` Michael Wang
2013-01-24 7:47 ` Mike Galbraith
2013-01-24 8:14 ` Michael Wang
2013-01-24 9:07 ` Mike Galbraith
2013-01-24 9:26 ` Michael Wang
2013-01-24 10:34 ` Mike Galbraith
2013-01-25 2:14 ` Michael Wang
2013-01-24 7:00 ` Michael Wang
2013-01-21 7:34 ` Michael Wang
2013-01-21 8:26 ` Mike Galbraith
2013-01-21 8:46 ` Michael Wang
2013-01-21 9:11 ` Mike Galbraith
2013-01-15 2:46 ` Michael Wang
2013-01-11 8:15 Michael Wang
2013-01-11 10:13 ` Nikunj A Dadhania
2013-01-15 2:20 ` 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=50FD08E1.8000302@linux.vnet.ibm.com \
--to=wangyun@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=bitbucket@online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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).