From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "tvrtko.ursulin@linux.intel.com" <tvrtko.ursulin@linux.intel.com>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [Intel-gfx 1/1] drm/i915/guc: Don't update engine busyness stats too frequently
Date: Fri, 17 Jun 2022 16:38:50 +0000 [thread overview]
Message-ID: <1a21b8a1b90fdb065e726011be008d6c9db19565.camel@intel.com> (raw)
In-Reply-To: <1a19781d-5d78-aa15-9578-44106433cbf9@linux.intel.com>
> Who did you find is doing the sampling in the real world use case? AFAIR
> if one one is querying busyness, I thought there would only be the GuC
> ping worker which runs extremely infrequently (to avoid some counter
> overflow).
>
> Regards,
>
> Tvrtko
>
> >
Hi Tvrtko, the case where we are launching many tiny transcode workloads in quick succession sees the gt_unpark/park
getting his hundreds or thousands of time - this is where the biggest hit comes from (as per the worst case example
number in the comment).
...alan
next prev parent reply other threads:[~2022-06-17 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 17:27 [Intel-gfx] [Intel-gfx 0/1] drm/i915/guc: Don't update engine busyness stats too frequently Alan Previn
2022-06-11 17:27 ` [Intel-gfx] [Intel-gfx 1/1] " Alan Previn
2022-06-13 8:10 ` Tvrtko Ursulin
2022-06-14 1:10 ` Umesh Nerlige Ramappa
2022-06-14 7:07 ` Tvrtko Ursulin
2022-06-15 18:59 ` Lucas De Marchi
2022-06-16 16:41 ` Tvrtko Ursulin
2022-06-17 16:38 ` Teres Alexis, Alan Previn [this message]
2022-06-17 21:43 ` Teres Alexis, Alan Previn
2022-06-20 8:38 ` Tvrtko Ursulin
2022-06-13 23:12 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/guc: Don't update engine busyness stats too frequently (rev2) Patchwork
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=1a21b8a1b90fdb065e726011be008d6c9db19565.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox