[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190716155852.GF32540@blackbody.suse.cz>
Date: Tue, 16 Jul 2019 17:58:52 +0200
From: Michal Koutný <mkoutny@...e.com>
To: Patrick Bellasi <patrick.bellasi@....com>
Cc: Alessio Balsini <balsini@...roid.com>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Morten Rasmussen <morten.rasmussen@....com>,
Quentin Perret <quentin.perret@....com>,
Joel Fernandes <joelaf@...gle.com>,
Paul Turner <pjt@...gle.com>,
Steve Muckle <smuckle@...gle.com>,
Suren Baghdasaryan <surenb@...gle.com>,
Todd Kjos <tkjos@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
Tejun Heo <tj@...nel.org>,
Vincent Guittot <vincent.guittot@...aro.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
Juri Lelli <juri.lelli@...hat.com>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org
Subject: Re: [PATCH v11 4/5] sched/core: uclamp: Use TG's clamps to restrict
TASK's clamps
On Tue, Jul 16, 2019 at 03:34:35PM +0100, Patrick Bellasi <patrick.bellasi@....com> wrote:
> Am I missing something?
No, it's rather my misinterpretation of the syscall semantics.
> Otherwise, I think the changelog sentence you quoted is just
> misleading.
It certainly mislead me to thinking about the sched_setattr calls as
requests of utilization being in the given interval (substituting 0 or 1 when
only one boundary is given, and further constrained by tg's interval).
I see your point, those are actually two (mostly) independent controls.
Makes sense now.
Thanks,
Michal
Powered by blists - more mailing lists