From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [PATCH v6 07/16] sched/core: uclamp: Add system default clamps Date: Wed, 23 Jan 2019 20:10:07 +0100 Message-ID: <20190123191007.GG17749@hirez.programming.kicks-ass.net> References: <20190115101513.2822-1-patrick.bellasi@arm.com> <20190115101513.2822-8-patrick.bellasi@arm.com> <20190122135644.GP27931@hirez.programming.kicks-ass.net> <20190122144329.ziimv6fejwvky7yb@e110439-lin> <20190122151317.GH13777@hirez.programming.kicks-ass.net> <20190122154129.mxnpgaoxnccbjbch@e110439-lin> <20190123092210.GU27931@hirez.programming.kicks-ass.net> <20190123141924.x36iqxh42lkssrxl@e110439-lin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20190123141924.x36iqxh42lkssrxl@e110439-lin> Sender: linux-kernel-owner@vger.kernel.org To: Patrick Bellasi Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, linux-api@vger.kernel.org, Ingo Molnar , Tejun Heo , "Rafael J . Wysocki" , Vincent Guittot , Viresh Kumar , Paul Turner , Quentin Perret , Dietmar Eggemann , Morten Rasmussen , Juri Lelli , Todd Kjos , Joel Fernandes , Steve Muckle , Suren Baghdasaryan List-Id: linux-api@vger.kernel.org On Wed, Jan 23, 2019 at 02:19:24PM +0000, Patrick Bellasi wrote: > On 23-Jan 10:22, Peter Zijlstra wrote: > > On Tue, Jan 22, 2019 at 03:41:29PM +0000, Patrick Bellasi wrote: > > > On 22-Jan 16:13, Peter Zijlstra wrote: > > > > On Tue, Jan 22, 2019 at 02:43:29PM +0000, Patrick Bellasi wrote: > > > > > > > Do you think that could be acceptable? > > > > > > > > Think so, it's a sysctl poke, 'nobody' ever does that. > > > > > > Cool, so... I'll keep lazy update for system default. > > > > Ah, I think I misunderstood. I meant to say that since nobody ever pokes > > at sysctl's it doesn't matter if its a little more expensive and iterate > > everything. > > Here I was more worried about the code complexity/overhead... for > something actually not very used/useful. > > > Also; if you always keep everything up-to-date, you can avoid doing that > > duplicate accounting. > > To update everything we will have to walk all the CPUs and update all > the RUNNABLE tasks currently enqueued, which are either RT or CFS. > > That's way more expensive both in code and time then what we do for > cgroups, where at least we have a limited scope since the cgroup > already provides a (usually limited) list of tasks to consider. > > Do you think it's really worth to have ? Dunno; the whole double bucket thing seems a bit weird to me; but maybe it will all look better without the mapping stuff.