public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Parth Shah <parth015@linux.vnet.ibm.com>
To: Dietmar Eggemann <dietmar.eggemann@arm.com>, linux-pm@vger.kernel.org
Subject: Re: [RFC 1/6] Optimize wake-up task for Task Packing heuristic
Date: Sun, 7 Apr 2019 11:27:19 +0530	[thread overview]
Message-ID: <60e34244-1e40-e318-080e-e76607bb3d92@linux.vnet.ibm.com> (raw)
In-Reply-To: <0b198386-ef0b-75e0-e53a-1160c77326b7@arm.com>



On 3/27/19 3:01 PM, Dietmar Eggemann wrote:
> Hi Parth,
> 
> On 3/22/19 7:06 AM, Parth Shah wrote:
>> TurboSched feature requires the minimal number of cores to be active
>> inorder to sustain higher Turbo-frequency in SMP sytems. The jitter
>> tasks if packed on the idle CPUs of already active cores will result in
>> better performance for throughput intensive workloads.
>>
>> Signed-off-by: Parth Shah <parth015@linux.vnet.ibm.com>
>> ---
>>   kernel/sched/fair.c | 91 ++++++++++++++++++++++++++++++++++++++++++++-
>>   1 file changed, 89 insertions(+), 2 deletions(-)
>>
>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>> index 51003e1c794d..dcf48f37e0fa 100644
>> --- a/kernel/sched/fair.c
>> +++ b/kernel/sched/fair.c
>> @@ -6202,6 +6202,82 @@ static int select_idle_cpu(struct task_struct *p, struct sched_domain *sd, int t
>>       return cpu;
>>   }
>>   +/*
>> + * Core is defined as under-utilized in case if the aggregated utilization of a
>> + * all the CPUs in a core is less than 12.5%
>> + */
>> +static inline bool core_underutilized(long unsigned core_util,
>> +           long unsigned core_capacity)
>> +{
>> +    return core_util < core_capacity>>3;
>> +}
>> +
>> +/*
>> + * Core Capacity Mulitplication Factor
>> + * The capacity of a core is defined to be 1.6x the capacity of any
>> + * CPU(or SM thread), since the architecture is symmetric
>> + */
>> +static const int core_cap_mf = 16;
>> +
>> +/*
>> + * Try to find non idle core in the system, but with spare capacity available
>> + * for task packing, thereby keeping minimal cores active.
>> + */
>> +static int select_non_idle_core(struct task_struct *p, int prev_cpu)
>> +{
>> +    struct cpumask *cpus = this_cpu_cpumask_var_ptr(select_idle_mask);
>> +    int core, smt;
>> +
>> +    cpumask_and(cpus, cpu_online_mask, &p->cpus_allowed);
>> +
>> +    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.


       reply	other threads:[~2019-04-07  5:57 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     ` Parth Shah [this message]
2019-04-10 16:33       ` [RFC 1/6] Optimize wake-up task for Task Packing heuristic Dietmar Eggemann
2019-04-11 14:05         ` Dietmar Eggemann
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-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
     [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

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=60e34244-1e40-e318-080e-e76607bb3d92@linux.vnet.ibm.com \
    --to=parth015@linux.vnet.ibm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=linux-pm@vger.kernel.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