[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAH9NwWe1XSY_HtYdn=TVMRQov0m5T2CNtKpY8UZqbf6OUZHV2Q@mail.gmail.com>
Date: Fri, 10 Jul 2020 14:21:41 +0200
From: Christian Gmeiner <christian.gmeiner@...il.com>
To: Lucas Stach <l.stach@...gutronix.de>
Cc: LKML <linux-kernel@...r.kernel.org>,
Chris Healy <cphealy@...il.com>,
Russell King <linux+etnaviv@...linux.org.uk>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
The etnaviv authors <etnaviv@...ts.freedesktop.org>,
DRI mailing list <dri-devel@...ts.freedesktop.org>
Subject: Re: [PATCH 0/4] Add support for GPU load values
Hi Lucas,
Am Fr., 10. Juli 2020 um 10:44 Uhr schrieb Christian Gmeiner
<christian.gmeiner@...il.com>:
>
> Hoi Lucas
>
> Am Fr., 10. Juli 2020 um 10:31 Uhr schrieb Lucas Stach <l.stach@...gutronix.de>:
> >
> > Hi Christian,
> >
> > Am Freitag, den 10.07.2020, 09:41 +0200 schrieb Christian Gmeiner:
> > > This patch series add support for loadavg values for GPU
> > > sub-components. I am adding a SMA algorithm as I was not
> > > really sure if EWMA would be a good fit for this use case.
> >
> > 1 second is a pretty long window in GPU time. Why do you feel that a
> > simple moving average is more appropriate than a exponentially
> > weighted one here? Note that I haven't given this any thought myself
> > and haven't made up my mind yet, so this is a honest question to
> > understand the reasoning behind your choice.
> >
>
I have v2 ready except for this point. If you want to go with EWMA could you
provide me with a good weight reciprocal value to use?
--
greets
--
Christian Gmeiner, MSc
https://christian-gmeiner.info/privacypolicy
Powered by blists - more mailing lists