From: Pavan Kondeti <pkondeti@codeaurora.org>
To: Patrick Bellasi <patrick.bellasi@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>, Tejun Heo <tj@kernel.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Paul Turner <pjt@google.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Juri Lelli <juri.lelli@redhat.com>, Todd Kjos <tkjos@google.com>,
Joel Fernandes <joelaf@google.com>,
Steve Muckle <smuckle@google.com>,
Suren Baghdasaryan <surenb@google.com>
Subject: Re: [PATCH v3 02/14] sched/core: uclamp: map TASK's clamp values into CPU's clamp groups
Date: Tue, 14 Aug 2018 16:55:09 +0530 [thread overview]
Message-ID: <20180814112509.GB2661@codeaurora.org> (raw)
In-Reply-To: <20180806163946.28380-3-patrick.bellasi@arm.com>
On Mon, Aug 06, 2018 at 05:39:34PM +0100, Patrick Bellasi wrote:
> Utilization clamping requires each CPU to know which clamp values are
> assigned to tasks that are currently RUNNABLE on that CPU.
> Multiple tasks can be assigned the same clamp value and tasks with
> different clamp values can be concurrently active on the same CPU.
> Thus, a proper data structure is required to support a fast and
> efficient aggregation of the clamp values required by the currently
> RUNNABLE tasks.
>
> For this purpose we use a per-CPU array of reference counters,
> where each slot is used to account how many tasks require a certain
> clamp value are currently RUNNABLE on each CPU.
> Each clamp value corresponds to a "clamp index" which identifies the
> position within the array of reference couters.
>
> :
> (user-space changes) : (kernel space / scheduler)
> :
> SLOW PATH : FAST PATH
> :
> task_struct::uclamp::value : sched/core::enqueue/dequeue
> : cpufreq_schedutil
> :
> +----------------+ +--------------------+ +-------------------+
> | TASK | | CLAMP GROUP | | CPU CLAMPS |
> +----------------+ +--------------------+ +-------------------+
> | | | clamp_{min,max} | | clamp_{min,max} |
> | util_{min,max} | | se_count | | tasks count |
> +----------------+ +--------------------+ +-------------------+
> :
> +------------------> : +------------------->
> group_id = map(clamp_value) : ref_count(group_id)
> :
> :
>
> Let's introduce the support to map tasks to "clamp groups".
> Specifically we introduce the required functions to translate a
> "clamp value" into a clamp's "group index" (group_id).
>
> Only a limited number of (different) clamp values are supported since:
> 1. there are usually only few classes of workloads for which it makes
> sense to boost/limit to different frequencies,
> e.g. background vs foreground, interactive vs low-priority
> 2. it allows a simpler and more memory/time efficient tracking of
> the per-CPU clamp values in the fast path.
>
> The number of possible different clamp values is currently defined at
> compile time. Thus, setting a new clamp value for a task can result into
> a -ENOSPC error in case this will exceed the number of maximum different
> clamp values supported.
>
I see that we drop reference on the previous clamp group when a task changes
its clamp limits. What about exiting tasks which claimed clamp groups? should
not we drop the reference?
Thanks,
Pavan
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2018-08-14 11:25 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 16:39 [PATCH v3 00/14] Add utilization clamping support Patrick Bellasi
2018-08-06 16:39 ` [PATCH v3 01/14] sched/core: uclamp: extend sched_setattr to support utilization clamping Patrick Bellasi
2018-08-06 16:50 ` Randy Dunlap
2018-08-09 8:39 ` Patrick Bellasi
2018-08-09 15:20 ` Randy Dunlap
2018-08-07 9:59 ` Juri Lelli
2018-08-13 12:14 ` Patrick Bellasi
2018-08-13 12:27 ` Juri Lelli
2018-08-07 12:35 ` Juri Lelli
2018-08-09 9:14 ` Patrick Bellasi
2018-08-09 9:50 ` Juri Lelli
2018-08-09 15:23 ` Patrick Bellasi
2018-08-10 7:50 ` Juri Lelli
2018-08-17 10:34 ` Quentin Perret
2018-08-17 10:57 ` Patrick Bellasi
2018-08-17 11:14 ` Quentin Perret
2018-08-06 16:39 ` [PATCH v3 02/14] sched/core: uclamp: map TASK's clamp values into CPU's clamp groups Patrick Bellasi
2018-08-14 11:25 ` Pavan Kondeti [this message]
2018-08-14 15:21 ` Patrick Bellasi
2018-08-06 16:39 ` [PATCH v3 03/14] sched/core: uclamp: add CPU's clamp groups accounting Patrick Bellasi
2018-08-14 15:44 ` Dietmar Eggemann
2018-08-14 16:49 ` Patrick Bellasi
2018-08-15 9:37 ` Dietmar Eggemann
2018-08-15 10:54 ` Patrick Bellasi
2018-08-15 10:59 ` Dietmar Eggemann
2018-08-16 13:32 ` Patrick Bellasi
2018-08-16 13:37 ` Quentin Perret
2018-08-16 13:45 ` Dietmar Eggemann
2018-08-16 14:21 ` Quentin Perret
2018-08-16 15:00 ` Dietmar Eggemann
2018-08-17 11:04 ` Patrick Bellasi
2018-08-06 16:39 ` [PATCH v3 04/14] sched/core: uclamp: update CPU's refcount on clamp changes Patrick Bellasi
2018-08-15 15:02 ` Dietmar Eggemann
2018-08-16 13:22 ` Patrick Bellasi
2018-08-06 16:39 ` [PATCH v3 05/14] sched/cpufreq: uclamp: add utilization clamping for FAIR tasks Patrick Bellasi
2018-08-08 13:18 ` Vincent Guittot
2018-08-09 15:30 ` Patrick Bellasi
2018-08-15 15:30 ` Dietmar Eggemann
2018-08-16 13:53 ` Patrick Bellasi
2018-08-06 16:39 ` [PATCH v3 06/14] sched/cpufreq: uclamp: add utilization clamping for RT tasks Patrick Bellasi
2018-08-07 13:26 ` Juri Lelli
2018-08-09 15:34 ` Patrick Bellasi
2018-08-09 16:03 ` Vincent Guittot
2018-08-13 10:12 ` Patrick Bellasi
2018-08-13 10:50 ` Juri Lelli
2018-08-13 12:07 ` Vincent Guittot
2018-08-13 12:09 ` Vincent Guittot
2018-08-13 12:49 ` Patrick Bellasi
2018-08-13 14:06 ` Vincent Guittot
2018-08-13 15:01 ` Patrick Bellasi
2018-08-16 10:34 ` Dietmar Eggemann
2018-08-16 13:40 ` Patrick Bellasi
2018-08-07 13:54 ` Quentin Perret
2018-08-09 15:41 ` Patrick Bellasi
2018-08-09 15:55 ` Quentin Perret
2018-08-13 10:17 ` Patrick Bellasi
2018-08-06 16:39 ` [PATCH v3 07/14] sched/core: uclamp: enforce last task UCLAMP_MAX Patrick Bellasi
2018-08-16 15:43 ` Dietmar Eggemann
2018-08-16 16:47 ` Patrick Bellasi
2018-08-16 17:10 ` Dietmar Eggemann
2018-08-16 17:27 ` Patrick Bellasi
2018-08-16 17:20 ` Patrick Bellasi
2018-08-06 16:39 ` [PATCH v3 08/14] sched/core: uclamp: extend cpu's cgroup controller Patrick Bellasi
2018-08-17 12:21 ` Dietmar Eggemann
2018-08-17 14:24 ` Patrick Bellasi
2018-08-06 16:39 ` [PATCH v3 09/14] sched/core: uclamp: propagate parent clamps Patrick Bellasi
2018-08-16 9:09 ` Pavan Kondeti
2018-08-16 14:07 ` Patrick Bellasi
2018-08-17 13:43 ` Dietmar Eggemann
2018-08-17 14:45 ` Patrick Bellasi
2018-08-17 15:50 ` Dietmar Eggemann
2018-08-20 10:01 ` Dietmar Eggemann
2018-08-20 12:28 ` Patrick Bellasi
2018-08-06 16:39 ` [PATCH v3 10/14] sched/core: uclamp: map TG's clamp values into CPU's clamp groups Patrick Bellasi
2018-08-06 16:39 ` [PATCH v3 11/14] sched/core: uclamp: use TG's clamps to restrict Task's clamps Patrick Bellasi
2018-08-06 16:39 ` [PATCH v3 12/14] sched/core: uclamp: add system default clamps Patrick Bellasi
2018-08-16 9:13 ` Pavan Kondeti
2018-08-16 14:37 ` Patrick Bellasi
2018-08-20 10:18 ` Dietmar Eggemann
2018-08-20 12:27 ` Patrick Bellasi
2018-08-06 16:39 ` [PATCH v3 13/14] sched/core: uclamp: update CPU's refcount on TG's clamp changes Patrick Bellasi
2018-08-06 16:39 ` [PATCH v3 14/14] sched/core: uclamp: use percentage clamp values Patrick Bellasi
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=20180814112509.GB2661@codeaurora.org \
--to=pkondeti@codeaurora.org \
--cc=dietmar.eggemann@arm.com \
--cc=joelaf@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=patrick.bellasi@arm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rafael.j.wysocki@intel.com \
--cc=smuckle@google.com \
--cc=surenb@google.com \
--cc=tj@kernel.org \
--cc=tkjos@google.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).