public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeffrey Hugo <jhugo@codeaurora.org>
To: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org
Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Austin Christ <austinwc@codeaurora.org>,
	Tyler Baicar <tbaicar@codeaurora.org>,
	Timur Tabi <timur@codeaurora.org>
Subject: Re: [PATCH V5 0/2] load_balance() fixes for affinity
Date: Tue, 20 Jun 2017 08:28:23 -0600	[thread overview]
Message-ID: <f424edfe-ee97-d5ea-d0f9-03cd9b33ddda@codeaurora.org> (raw)
In-Reply-To: <0189c03c-03c8-b5ba-d986-ea64b09398fc@codeaurora.org>

On 6/13/2017 8:32 AM, Jeffrey Hugo wrote:
> On 6/7/2017 1:18 PM, Jeffrey Hugo wrote:
>> Co-authored-by: Austin Christ <austinwc@codeaurora.org>
>> Signed-off-by: Jeffrey Hugo <jhugo@codeaurora.org>
>>
>> [V5]
>> -updated comment to explain the "why" behind the redo check
>> -fixed panic triggered from active_load_balance_cpu_stop()
>>
>> [V4]
>> -restricted active cpus mask to the domain span
>> -fixed dst_cpu masking logic to work for the entire local group
>>
>> [V3]
>> -fixed botched subject lines
>>
>> [V2]
>> -Corrected use of Signed-off-by tags
>> -Removed temp cpumask variable from stack
>>
>> Jeffrey Hugo (2):
>>    sched/fair: Fix load_balance() affinity redo path
>>    sched/fair: Remove group imbalance from calculate_imbalance()
>>
>>   kernel/sched/fair.c | 22 ++++++++++++----------
>>   1 file changed, 12 insertions(+), 10 deletions(-)
>>
> 
> Peter (and/or Ingo?), is this series likely to make 4.13?  V5 has been 
> quiet, so I'm not sure if folks are happy with things, or just haven't 
> had time to review.
> 
> Thanks
> 

Ping?

-- 
Jeffrey Hugo
Qualcomm Datacenter Technologies as an affiliate of Qualcomm 
Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.

  reply	other threads:[~2017-06-20 14:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 19:18 [PATCH V5 0/2] load_balance() fixes for affinity Jeffrey Hugo
2017-06-07 19:18 ` [PATCH V5 1/2] sched/fair: Fix load_balance() affinity redo path Jeffrey Hugo
2017-07-05 11:22   ` Peter Zijlstra
2017-07-05 22:48   ` [tip:sched/urgent] " tip-bot for Jeffrey Hugo
2017-06-07 19:18 ` [PATCH V5 2/2] sched/fair: Remove group imbalance from calculate_imbalance() Jeffrey Hugo
2017-07-05 11:22   ` Peter Zijlstra
2017-07-07 15:26     ` Jeffrey Hugo
2017-06-13 14:32 ` [PATCH V5 0/2] load_balance() fixes for affinity Jeffrey Hugo
2017-06-20 14:28   ` Jeffrey Hugo [this message]
2017-06-28 16:12     ` Jeffrey Hugo
2017-07-05  9:19       ` Peter Zijlstra

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=f424edfe-ee97-d5ea-d0f9-03cd9b33ddda@codeaurora.org \
    --to=jhugo@codeaurora.org \
    --cc=austinwc@codeaurora.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tbaicar@codeaurora.org \
    --cc=timur@codeaurora.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