From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Uladzislau Rezki <urezki@gmail.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Uladzislau 2 Rezki <uladzislau2.rezki@sonymobile.com>
Subject: Re: [RFC,v2 3/3] sched: ignore task_h_load for CPU_NEWLY_IDLE
Date: Wed, 15 Feb 2017 18:58:46 +0000 [thread overview]
Message-ID: <1f0bc6a4-7e17-98bf-2ef0-a805e32a5591@arm.com> (raw)
In-Reply-To: <CA+KHdyVM+U-SA-6R9zU1t3SR44L3uMbXKMuwSk4XLo3JpkVZDw@mail.gmail.com>
On 02/14/2017 06:28 PM, Uladzislau Rezki wrote:
>>>
>>> So that is useful information that should have been in the Changelog.
>>>
>>> OK, can you respin this patch with adjusted Changelog and taking Mike's
>>> feedback?
>>>
>> Yes, i will prepare a patch accordingly, no problem.
>>
>>>
>>> Also, I worry about the effects of this on !PREEMPT kernels, the first
>>> hunk (which explicitly states is about latency) should be under
>>> CONFIG_PREEMPT to match the similar case we already have in
>>> detach_tasks().
This one uses #ifdef CONFIG_PREEMPT whereas you use
IS_ENABLED(CONFIG_PREEMPT). Is there a particular reason for this?
>>> But your second hunk, which ignores the actual load of tasks in favour
>>> of just moving _something_ already, is utterly dangerous if not coupled
>>> with these two other conditions, so arguably that too should be under
>>> CONFIG_PREEMPT.
>>>
>> I see your point. Will round both with CONFIG_PREEMPT.
>>
> I have upload a new patch, please find it here:
> https://lkml.org/lkml/2017/2/14/334
>
next prev parent reply other threads:[~2017-02-15 18:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 8:43 [RFC,v2 1/3] sched: set loop_max after rq lock is taken Uladzislau Rezki
2017-02-08 8:43 ` [RFC,v2 2/3] sched: set number of iterations to h_nr_running Uladzislau Rezki
2017-02-09 12:20 ` Peter Zijlstra
2017-02-09 18:59 ` Uladzislau Rezki
2017-02-08 8:43 ` [RFC,v2 3/3] sched: ignore task_h_load for CPU_NEWLY_IDLE Uladzislau Rezki
2017-02-08 9:19 ` Mike Galbraith
2017-02-09 10:12 ` Uladzislau Rezki
2017-02-09 12:22 ` Peter Zijlstra
2017-02-09 18:54 ` Uladzislau Rezki
2017-02-13 13:51 ` Peter Zijlstra
2017-02-13 17:17 ` Uladzislau Rezki
2017-02-14 18:28 ` Uladzislau Rezki
2017-02-15 18:58 ` Dietmar Eggemann [this message]
2017-02-16 11:20 ` Uladzislau Rezki
2017-03-08 15:35 ` Uladzislau Rezki
2017-02-09 12:14 ` [RFC,v2 1/3] sched: set loop_max after rq lock is taken 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=1f0bc6a4-7e17-98bf-2ef0-a805e32a5591@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=uladzislau2.rezki@sonymobile.com \
--cc=urezki@gmail.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
all inboxes | Powered by JetHome®