From: Uladzislau Rezki <urezki@gmail.com>
To: 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 2/3] sched: set number of iterations to h_nr_running
Date: Thu, 9 Feb 2017 19:59:24 +0100 [thread overview]
Message-ID: <CA+KHdyXrAMkBa4b4naHhUARTK2SwbqmG8RORz5=fE2xq-vULNw@mail.gmail.com> (raw)
In-Reply-To: <20170209122005.GD6500@twins.programming.kicks-ass.net>
On Thu, Feb 9, 2017 at 1:20 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, Feb 08, 2017 at 09:43:28AM +0100, Uladzislau Rezki wrote:
>> From: Uladzislau 2 Rezki <uladzislau2.rezki@sonymobile.com>
>>
>> It is possible that busiest run queue has multiple RT tasks,
>> whereas no CFS tasks, that is why it is reasonable to use
>> h_nr_running instead, because a load balance only applies
>> for CFS related tasks.
>
>
> Sure, I suppose that makes sense, but then it would make even more sense
> to do a more thorough audit of the code and make sure all remaining
> rq::nr_running uses are correct.
>
Indeed. I did not want to touch othe places, due to my specific test case.
There are still a few raming places. I can prepare a new patch that covers
all of them if that is ok.
--
Uladzislau Rezki
next prev parent reply other threads:[~2017-02-09 19:00 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 [this message]
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
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='CA+KHdyXrAMkBa4b4naHhUARTK2SwbqmG8RORz5=fE2xq-vULNw@mail.gmail.com' \
--to=urezki@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=uladzislau2.rezki@sonymobile.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).