From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Bellasi Subject: Re: [PATCH v7 01/15] sched/core: uclamp: Add CPU's clamp buckets refcounting Date: Thu, 14 Mar 2019 15:40:52 +0000 Message-ID: <20190314154052.345v74snhtc4cqbe@e110439-lin> References: <20190208100554.32196-1-patrick.bellasi@arm.com> <20190208100554.32196-2-patrick.bellasi@arm.com> <20190314144600.2ulpeipad7jbxyiy@e110439-lin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Suren Baghdasaryan Cc: LKML , linux-pm@vger.kernel.org, linux-api@vger.kernel.org, Ingo Molnar , Peter Zijlstra , 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 List-Id: linux-api@vger.kernel.org On 14-Mar 08:29, Suren Baghdasaryan wrote: > On Thu, Mar 14, 2019 at 7:46 AM Patrick Bellasi wrote: > > On 13-Mar 14:32, Suren Baghdasaryan wrote: > > > On Fri, Feb 8, 2019 at 2:06 AM Patrick Bellasi wrote: [...] > > > > The rq::uclamp::bucket[clamp_id][] array is scanned every time we need > > > > to find a new MAX aggregated clamp value for a clamp_id. This operation > > > > is required only when we dequeue the last task of a clamp bucket > > > > tracking the current MAX aggregated clamp value. In these cases, the CPU > > > > is either entering IDLE or going to schedule a less boosted or more > > > > clamped task. The following: > > > > The expected number of different clamp values, configured at build time, > > > > is small enough to fit the full unordered array into a single cache > > > > line. will read: The expected number of different clamp values, configured at build time, is small enough to fit the full unordered array into a single cache line for the default UCLAMP_BUCKETS configuration of 7 buckets. [...] > Got it. From reading the documentation at the beginning my impression > was that whatever value I choose within allowed 5-20 range it would > still fit in a cache line. To disambiguate it might be worse > mentioning that this is true for the default value or for values up to > 7. Thanks! Right, I hope the above proposed change helps to clarify that. -- #include Patrick Bellasi