All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Gmeiner <christian.gmeiner@gmail.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	David Airlie <airlied@linux.ie>,
	"moderated list:DRM DRIVERS FOR VIVANTE GPU IP" 
	<etnaviv@lists.freedesktop.org>,
	"open list:DRM DRIVERS FOR VIVANTE GPU IP" 
	<dri-devel@lists.freedesktop.org>,
	Daniel Vetter <daniel@ffwll.ch>,
	Russell King <linux+etnaviv@armlinux.org.uk>
Subject: Re: [PATCH v2 4/4] drm/etnaviv: export loadavg via perfmon
Date: Sat, 2 Jul 2022 13:57:43 +0200	[thread overview]
Message-ID: <CAH9NwWc7x2nUQAhL4vpeOJ-gRUHs4QqqBeo4jbQt0e2Mb=a7_w@mail.gmail.com> (raw)
In-Reply-To: <2d475e77dca2395ee5b6fcff0e1d3ade2b0a36ef.camel@pengutronix.de>

Hi Lucas

> You need to explain a bit more how you intend to use those.
>
> Contrary to all other perfmon values, where we go to great lengths to
> only count the load put onto the GPU by the specific process requesting
> the perfmon, the loadavg values also include the load caused by other
> submits. Due to this difference in behavior I fear that those new
> counters might be confusing to use. But maybe you have a use-case in
> mind that I don't see right now.

I see these values as total load avg of a sub-GPU component. Sure it is not per
process but it is a starting point. I have no problem introducing per
process load avg
values .. lets see how the next version of this series will look like,

-- 
greets
--
Christian Gmeiner, MSc

https://christian-gmeiner.info/privacypolicy

WARNING: multiple messages have this Message-ID (diff)
From: Christian Gmeiner <christian.gmeiner@gmail.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: David Airlie <airlied@linux.ie>,
	LKML <linux-kernel@vger.kernel.org>,
	"open list:DRM DRIVERS FOR VIVANTE GPU IP"
	<dri-devel@lists.freedesktop.org>,
	"moderated list:DRM DRIVERS FOR VIVANTE GPU IP"
	<etnaviv@lists.freedesktop.org>,
	Russell King <linux+etnaviv@armlinux.org.uk>
Subject: Re: [PATCH v2 4/4] drm/etnaviv: export loadavg via perfmon
Date: Sat, 2 Jul 2022 13:57:43 +0200	[thread overview]
Message-ID: <CAH9NwWc7x2nUQAhL4vpeOJ-gRUHs4QqqBeo4jbQt0e2Mb=a7_w@mail.gmail.com> (raw)
In-Reply-To: <2d475e77dca2395ee5b6fcff0e1d3ade2b0a36ef.camel@pengutronix.de>

Hi Lucas

> You need to explain a bit more how you intend to use those.
>
> Contrary to all other perfmon values, where we go to great lengths to
> only count the load put onto the GPU by the specific process requesting
> the perfmon, the loadavg values also include the load caused by other
> submits. Due to this difference in behavior I fear that those new
> counters might be confusing to use. But maybe you have a use-case in
> mind that I don't see right now.

I see these values as total load avg of a sub-GPU component. Sure it is not per
process but it is a starting point. I have no problem introducing per
process load avg
values .. lets see how the next version of this series will look like,

-- 
greets
--
Christian Gmeiner, MSc

https://christian-gmeiner.info/privacypolicy

  reply	other threads:[~2022-07-02 11:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21  7:20 [PATCH v2 0/4] Add support for GPU load values Christian Gmeiner
2022-06-21  7:20 ` Christian Gmeiner
2022-06-21  7:20 ` [PATCH v2 1/4] drm/etnaviv: add simple moving average (SMA) Christian Gmeiner
2022-06-21  7:20   ` Christian Gmeiner
2022-06-24  9:22   ` Lucas Stach
2022-06-24  9:22     ` Lucas Stach
2022-07-02 11:41     ` Christian Gmeiner
2022-07-02 11:41       ` Christian Gmeiner
2022-06-21  7:20 ` [PATCH v2 2/4] drm/etnaviv: add loadavg accounting Christian Gmeiner
2022-06-21  7:20   ` Christian Gmeiner
2022-06-24  9:38   ` Lucas Stach
2022-06-24  9:38     ` Lucas Stach
2022-07-02 11:53     ` Christian Gmeiner
2022-07-02 11:53       ` Christian Gmeiner
2022-06-21  7:20 ` [PATCH v2 3/4] drm/etnaviv: show loadavg in debugfs Christian Gmeiner
2022-06-21  7:20   ` Christian Gmeiner
2022-06-21  7:20 ` [PATCH v2 4/4] drm/etnaviv: export loadavg via perfmon Christian Gmeiner
2022-06-21  7:20   ` Christian Gmeiner
2022-06-24  9:44   ` Lucas Stach
2022-06-24  9:44     ` Lucas Stach
2022-07-02 11:57     ` Christian Gmeiner [this message]
2022-07-02 11:57       ` Christian Gmeiner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH9NwWc7x2nUQAhL4vpeOJ-gRUHs4QqqBeo4jbQt0e2Mb=a7_w@mail.gmail.com' \
    --to=christian.gmeiner@gmail.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=etnaviv@lists.freedesktop.org \
    --cc=l.stach@pengutronix.de \
    --cc=linux+etnaviv@armlinux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.