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 2/6] Provide cgroup interface for manual jitter classification
Date: Mon, 15 Apr 2019 12:53:50 +0530	[thread overview]
Message-ID: <f14f03e4-33e9-06a0-ca81-fbfb07ae22d5@linux.vnet.ibm.com> (raw)
In-Reply-To: <462cf628-1b0b-4f8c-251d-c0cff6af18fd@arm.com>



On 4/11/19 7:16 PM, Dietmar Eggemann wrote:
> On 3/22/19 7:06 AM, Parth Shah wrote:
>> Signed-off-by: Parth Shah <parth015@linux.vnet.ibm.com>
>> ---
>>   include/linux/sched.h |  8 ++++++++
>>   kernel/sched/core.c   | 46 +++++++++++++++++++++++++++++++++++++++++++
>>   kernel/sched/fair.c   | 15 +++++++++-----
>>   kernel/sched/sched.h  |  2 ++
>>   4 files changed, 66 insertions(+), 5 deletions(-)
>>
>> diff --git a/include/linux/sched.h b/include/linux/sched.h
>> index 903ef29b62c3..be8e8617e0cb 100644
>> --- a/include/linux/sched.h
>> +++ b/include/linux/sched.h
>> @@ -604,6 +604,14 @@ struct task_struct {
>>       unsigned int            flags;
>>       unsigned int            ptrace;
>>   +    /*
>> +     * task_characteristics:
>> +     * 0 = unknown. Follows regular CFS policy for task placement.
>> +     * 1 = Throughput intensive high utilization task
>> +     * 2 = Jitter tasks. Should be packed to reduce active core count.
> 
> This is very similar to the ideas in [PATCH v8 00/16] Add utilization clamping support https://lore.kernel.org/lkml/20190402104153.25404-1-patrick.bellasi@arm.com . Task classification from userspace ...
> 
> [...]
> 

Patches seems interesting and converges to the process of jitter classification.
I will try to re-base my patches on top of that.

Thanks


  reply	other threads:[~2019-04-15  7:23 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
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 [this message]
     [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=f14f03e4-33e9-06a0-ca81-fbfb07ae22d5@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