[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20200805124128.kfx7uofqnrtk6kux@e107158-lin.cambridge.arm.com>
Date: Wed, 5 Aug 2020 13:41:29 +0100
From: Qais Yousef <qais.yousef@....com>
To: Dongdong Yang <contribute.kernel@...il.com>
Cc: Greg KH <gregkh@...uxfoundation.org>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
Viresh Kumar <viresh.kumar@...aro.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"peterz@...radead.org" <peterz@...radead.org>,
"juri.lelli@...hat.com" <juri.lelli@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <Dietmar.Eggemann@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Benjamin Segall <bsegall@...gle.com>,
"mgorman@...e.de" <mgorman@...e.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"yangdongdong@...omi.com" <yangdongdong@...omi.com>,
"yanziily@...omi.com" <yanziily@...omi.com>,
"rocking@...ux.alibaba.com" <rocking@...ux.alibaba.com>
Subject: Re: [PATCH v4] sched: Provide USF for the portable equipment.
On 08/05/20 19:13, Dongdong Yang wrote:
> Appreciate Qais for your clamp implementation. I would like to add traces
> for uclamp_rq_util_with and feedback you if I run into any issues.
Thanks.
FYI, top posting in LKML is frowned upon. Please put your answer underneath the
quoted text.
>
> The util would not be adjusted as soon as FB screen on notification be
> received by USF from kernel level if it is set by sched_usf_non_ux, no
> matter whether screen on or off. However, sched_util_clamp_min/max have not
> been recovered until user space screen on detection. The screen on response
> would not be in time for the sensitive user when many background tasks are
> running. Whether the kernel module could also
> set sched_util_clamp_min/max?
For boosting, are you just changing the sysctl or are you actively using
sched_setattr() to boost tasks too?
Please have a look at the documentation for the sysctl interface.
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/tree/Documentation/admin-guide/sysctl/kernel.rst?h=sched/core#n1065
In summary, they just control the _allowed_ levels. So you can use it to
cap/throttle the maximum performance level the system is running at. But you
can't use it to boost the whole system. You must use the sched_setattr() to
boost important tasks individually or if all the tasks are in a cgroup you
can use that. For cgroup interface there's a caveat. If you want to use it
let me know so I can explain how boosting would work there.
I advise to use the sched_setattr() interface to target and boost those
important tasks only. You can as well be smart and target all the background
tasks to cap them via sched_setattr(). In this case you wouldn't have to modify
the sysctl_sched_util_clamp_min/max.
I don't see uclamp being a suitable interface for in-kernel users. PM_QOS is
more suitable in my opinion for in-kernel users if you want to impact the
overall system performance.
I might have misunderstood what you were saying above. If so, can you please
rephrase?
Thanks
--
Qais Yousef
Powered by blists - more mailing lists