From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Parth Shah <parth015@linux.vnet.ibm.com>, linux-pm@vger.kernel.org
Subject: Re: [RFC 1/6] Optimize wake-up task for Task Packing heuristic
Date: Thu, 11 Apr 2019 16:05:11 +0200 [thread overview]
Message-ID: <f45f53c6-1200-35dc-580b-67d2062152ab@arm.com> (raw)
In-Reply-To: <c877a201-2601-5bf4-7c80-0f6b190c1711@arm.com>
On 4/10/19 6:33 PM, Dietmar Eggemann wrote:
> On 4/7/19 7:57 AM, Parth Shah wrote:
>>
>>
>> On 3/27/19 3:01 PM, Dietmar Eggemann wrote:
>>> Hi Parth,
>>>
>>> On 3/22/19 7:06 AM, Parth Shah wrote:
>
> [...]
>
>>>> + for_each_cpu_wrap(core, cpus, prev_cpu)
>>>> + {
>>>> + long unsigned int core_util = 0;
>>>> + long unsigned int core_cap = core_cap_mf*capacity_of(core)/10;
>>>> + long unsigned int cache_cpu_util = (unsigned)-1;
>>>> + long unsigned est_util = 0, est_util_enqueued = 0;
>>>> + int cache_cpu = core;
>>>> + struct cfs_rq *cfs_rq;
>>>> +
>>>> + for_each_cpu(smt, cpu_smt_mask(core)) {
>>>
>>> This one doesn't build for me on arm64 (make defconfig) since it uses
>>> cpu_smt_mask() outside the CONFIG_SCHED_SMT guard.
>>>
>>> kernel/sched/fair.c: In function ‘select_non_idle_core’:
>>> kernel/sched/fair.c:6243:21: error: implicit declaration of function
>>> ‘cpu_smt_mask’; did you mean ‘cpu_cpu_mask’?
>>> [-Werror=implicit-function-declaration]
>>> for_each_cpu(smt, cpu_smt_mask(core)) {
>>> ^
>>> ./include/linux/cpumask.h:242:32: note: in definition of macro
>>> ‘for_each_cpu’
>>>
>>> [...]
>>>
>>
>> Thanks for pointing out. It will not build for individual patches for
>> the current version of RFC.
>>
>> Please try to build it with full patch set. I assure, the following
>> iterations of RFC will resolve this issue.
>
> Ah, I see, you have this CONFIG_TURBO_SCHED patch at the end of the
> series. I think that you will have a hard time to get new CONFIG
> switches into the task scheduler code. Can you not bting in your feature
> w/o CONFIG_TURBO_SCHED?
I think you could replace CONFIG_TURBO_SCHED entirely with your static
key __turbo_sched_enabled (and the existing CONFIG_SMT in case your
feature relies on SMT).
Please sent your next version to linux-kernel@vger.kernel.org as well
and cc the task scheduler maintainer to get more review.
next prev parent reply other threads:[~2019-04-11 14:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190322060621.27021-1-parth015@linux.vnet.ibm.com>
[not found] ` <20190322060621.27021-2-parth015@linux.vnet.ibm.com>
[not found] ` <0b198386-ef0b-75e0-e53a-1160c77326b7@arm.com>
2019-04-07 5:57 ` [RFC 1/6] Optimize wake-up task for Task Packing heuristic Parth Shah
2019-04-10 16:33 ` Dietmar Eggemann
2019-04-11 14:05 ` Dietmar Eggemann [this message]
2019-04-11 14:44 ` Parth Shah
[not found] ` <20190322060621.27021-4-parth015@linux.vnet.ibm.com>
[not found] ` <001101d4e35c$13951220$3abf3660$@net>
[not found] ` <20190404095854.GB25302@aks.ibm>
2019-04-07 6:43 ` [RFC 3/6] Introduce static key to enable or disable TurboSched Parth Shah
[not found] ` <20190322060621.27021-7-parth015@linux.vnet.ibm.com>
2019-04-10 16:39 ` [RFC 6/6] Providing TurboSched as config option Dietmar Eggemann
[not found] ` <20190322060621.27021-3-parth015@linux.vnet.ibm.com>
2019-04-11 13:46 ` [RFC 2/6] Provide cgroup interface for manual jitter classification Dietmar Eggemann
2019-04-15 7:23 ` Parth Shah
[not found] ` <20190322060621.27021-5-parth015@linux.vnet.ibm.com>
2019-04-11 15:54 ` [RFC 4/6] Add cpumask to track throughput intensive tasks Dietmar Eggemann
2019-04-12 10:47 ` Dietmar Eggemann
2019-04-12 11:16 ` Parth Shah
2019-04-12 10:58 ` Dietmar Eggemann
2019-04-12 11:31 ` Parth Shah
2019-04-12 11:13 ` Dietmar Eggemann
2019-04-12 11:23 ` Parth Shah
[not found] ` <20190322060621.27021-6-parth015@linux.vnet.ibm.com>
2019-04-11 16:01 ` [RFC 5/6] Improvise cgroup interface for classifying jitter from WOF tasks Dietmar Eggemann
2019-04-12 11:28 ` Parth Shah
2019-04-12 13:08 ` Dietmar Eggemann
2019-04-12 15:48 ` Parth Shah
2019-04-15 10:27 ` Dietmar Eggemann
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=f45f53c6-1200-35dc-580b-67d2062152ab@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=linux-pm@vger.kernel.org \
--cc=parth015@linux.vnet.ibm.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