On Wed, Dec 02, 2020 at 04:45:31PM +, Mel Gorman wrote:
> > > It's less obvious what the consequence is unless the reader manages to
> > > tie the IO-wait comment in "Schedutil / DVFS" to this section.
> >
> > I'm not entirely sure I follow. The purpose of UTIL_EST is to avoid
> > ramp-up iss
On Wed, Dec 02, 2020 at 04:54:52PM +0100, Peter Zijlstra wrote:
> > IIRC, this 32ms is tied to the value of LOAD_AVG_PERIOD and the length
> > of the ewma_sum series below. Might be worth expanding a little further.
>
> It is LOAD_AVG_PERIOD. Some people (re)generate the PELT tables with a
> diffe
On Wed, Dec 02, 2020 at 02:18:35PM +, Mel Gorman wrote:
> For whatever reason, this only arrived in my inbox today.
It's as if the gods of email knew you was busy before ;-)
> On Fri, Nov 20, 2020 at 08:55:27AM +0100, Peter Zijlstra wrote:
> > PELT (Per Entity Load Tracking)
> > -
For whatever reason, this only arrived in my inbox today.
On Fri, Nov 20, 2020 at 08:55:27AM +0100, Peter Zijlstra wrote:
> PELT (Per Entity Load Tracking)
> ---
>
> With PELT we track some metrics across the various entities, from individual
s/entities/scheduler enti
On 23/11/2020 14:42, Vincent Guittot wrote:
> On Mon, 23 Nov 2020 at 12:27, Dietmar Eggemann
> wrote:
>>
>> On 23/11/2020 11:05, Vincent Guittot wrote:
>>> On Mon, 23 Nov 2020 at 10:30, Dietmar Eggemann
>>> wrote:
On 20/11/2020 09:56, Peter Zijlstra wrote:
> On Fri, Nov 20, 2020 a
On Mon, Nov 23, 2020 at 10:26:13AM +0100, Dietmar Eggemann wrote:
> On 20/11/2020 08:55, Peter Zijlstra wrote:
>
> [...]
>
> > PELT (Per Entity Load Tracking)
> > ---
>
> [...]
>
> > Using this we track 2 key metrics: 'running' and 'runnable'. 'Running'
> > reflects
On Mon, 23 Nov 2020 at 12:27, Dietmar Eggemann wrote:
>
> On 23/11/2020 11:05, Vincent Guittot wrote:
> > On Mon, 23 Nov 2020 at 10:30, Dietmar Eggemann
> > wrote:
> >>
> >> On 20/11/2020 09:56, Peter Zijlstra wrote:
> >>> On Fri, Nov 20, 2020 at 08:55:27AM +0100, Peter Zijlstra wrote:
> -
On 23/11/2020 11:05, Vincent Guittot wrote:
> On Mon, 23 Nov 2020 at 10:30, Dietmar Eggemann
> wrote:
>>
>> On 20/11/2020 09:56, Peter Zijlstra wrote:
>>> On Fri, Nov 20, 2020 at 08:55:27AM +0100, Peter Zijlstra wrote:
- In saturated scenarios task movement will cause some transient dips,
>
On Mon, 23 Nov 2020 at 10:30, Dietmar Eggemann wrote:
>
> On 20/11/2020 09:56, Peter Zijlstra wrote:
> > On Fri, Nov 20, 2020 at 08:55:27AM +0100, Peter Zijlstra wrote:
> >> - In saturated scenarios task movement will cause some transient dips,
> >>suppose we have a CPU saturated with 4 tasks
On 20/11/2020 09:56, Peter Zijlstra wrote:
> On Fri, Nov 20, 2020 at 08:55:27AM +0100, Peter Zijlstra wrote:
>> - In saturated scenarios task movement will cause some transient dips,
>>suppose we have a CPU saturated with 4 tasks, then when we migrate a task
>>to an idle CPU, the old CPU w
On 20/11/2020 08:55, Peter Zijlstra wrote:
[...]
> PELT (Per Entity Load Tracking)
> ---
[...]
> Using this we track 2 key metrics: 'running' and 'runnable'. 'Running'
> reflects the time an entity spends on the CPU, while 'runnable' reflects the
> time an entity spe
Hi Peter,
Looks like a nice summary to me.
On Fri, Nov 20, 2020 at 08:55:27AM +0100, Peter Zijlstra wrote:
> Hi,
>
> I was recently asked to explain how schedutil works, the below write-up
> is the result of that and I figured we might as well stick it in the
> tree.
>
> Not as a patch for easy
Hi,
On 20/11/20 07:55, Peter Zijlstra wrote:
> Frequency- / Heterogeneous Invariance
> -
>
> Because consuming the CPU for 50% at 1GHz is not the same as consuming the CPU
> for 50% at 2GHz, nor is running 50% on a LITTLE CPU the same as running 50% on
> a big
On Friday 20 Nov 2020 at 14:49:04 (+0530), Viresh Kumar wrote:
> This is unlikely to be an issue on systems where cpufreq policies are
> shared between multiple CPUs, because in those cases the policy
> utilization is computed as the maximum of the CPU utilization values
> over the
On 20-11-20, 09:13, Quentin Perret wrote:
> On Friday 20 Nov 2020 at 09:56:53 (+0100), Peter Zijlstra wrote:
> > On Fri, Nov 20, 2020 at 08:55:27AM +0100, Peter Zijlstra wrote:
> > > - In saturated scenarios task movement will cause some transient dips,
> > >suppose we have a CPU saturated wit
On Friday 20 Nov 2020 at 09:56:53 (+0100), Peter Zijlstra wrote:
> On Fri, Nov 20, 2020 at 08:55:27AM +0100, Peter Zijlstra wrote:
> > - In saturated scenarios task movement will cause some transient dips,
> >suppose we have a CPU saturated with 4 tasks, then when we migrate a task
> >to a
On Fri, Nov 20, 2020 at 08:55:27AM +0100, Peter Zijlstra wrote:
> - In saturated scenarios task movement will cause some transient dips,
>suppose we have a CPU saturated with 4 tasks, then when we migrate a task
>to an idle CPU, the old CPU will have a 'running' value of 0.75 while the
>
17 matches
Mail list logo
