From: Peter Clifton <pcjc2@cam.ac.uk>
To: Eric Anholt <eric@anholt.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: intel_gpu_top decode..
Date: Thu, 07 Oct 2010 13:55:02 +0100 [thread overview]
Message-ID: <1286456102.20269.31.camel@pcjc2lap> (raw)
In-Reply-To: <877hhvq7me.fsf@pollan.anholt.net>
[-- Attachment #1: Type: text/plain, Size: 11405 bytes --]
On Wed, 2010-10-06 at 15:27 -0700, Eric Anholt wrote:
> Of this, I'd say that you're spending a surprising amount of time in
> texture fetch. Finding ways to reduce texture bandwidth may pay off,
> assuming that (texture fetch / sampler cache) is the percentage of the
> time you're cache missing. I'm not sure if that's true or not, though.
> And you said that this data was just for the line drawing, which didn't
> appear to have any texturing going on at all, so I'm just confused.
I cut down my rendering code to almost nothing (just draw a blank
full-viewport quad 30 times):
int count = 0;
glBegin (GL_QUADS);
for (count = 0; count < 30; count++) {
glVertex3i (0, 0, 0);
glVertex3i (PCB->MaxWidth, 0, 0);
glVertex3i (PCB->MaxWidth, PCB->MaxHeight, 0);
glVertex3i (0, PCB->MaxHeight, 0);
}
glEnd ();
and was able to get this trace:
Texture unit %busy seems to go up with increasing count above.
core clock: 400 Mhz
ring idle: 3%: █▍
ring space: 60/126976 (0%)
task percent busy
UC0 CS: 93%: █████████████████████████████████████▍
VF CS: 92%: █████████████████████████████████████
Row 1, EU 3: 92%: █████████████████████████████████████
Windowizer: 92%: █████████████████████████████████████
Row 0, EU 3: 92%: █████████████████████████████████████
Row 1, EU 2: 92%: █████████████████████████████████████
Row 0, EU 2: 92%: █████████████████████████████████████
Setup Engine: 92%: █████████████████████████████████████
Row 1, EU 1: 92%: █████████████████████████████████████
ISC CS: 92%: █████████████████████████████████████
Row 0, EU 1: 92%: █████████████████████████████████████
Row 1, EU 0: 92%: █████████████████████████████████████
Bypass FIFO: 92%: █████████████████████████████████████
Map filter: 92%: █████████████████████████████████████
Pixel shader: 92%: █████████████████████████████████████
Filtering: 92%: █████████████████████████████████████
CL CS: 79%: ███████████████████████████████▊
Texture decompress: 76%: ██████████████████████████████▌
Texture fetch: 74%: █████████████████████████████▊
Sampler cache: 73%: █████████████████████████████▍
GS CS: 70%: ████████████████████████████▏
URB CS: 69%: ███████████████████████████▊
VS0 CS: 54%: █████████████████████▊
Projection and LOD: 50%: ████████████████████▏
Dispatcher: 39%: ███████████████▊
Dependent address generator: 38%: ███████████████▍
Message Arbiter row 1: 19%: ███████▊
EM1 CS CR: 7%: ███
SVDR CS CR: 4%: █▊
SVSM CS CR: 1%: ▌
SVTW CS CR: 0%: ▏
GW CS CR: 0%: ▏
UC1 CS: 0%: ▏
SVRW CS CR: 0%: ▏
SVRR CS CR: 0%: ▏
EM0 CS CR: 0%: ▏
MAW CS CR: 0%: ▏
MASM CS CR: 0%: ▏
SVDW CS CR: 0%: ▏
This was just with the following rendering code (and the fragment shader
I posted before, FF vertex pipeline). Without the fragment shader, I got
this (similar) trace:
UC0 CS: 82%: █████████████████████████████████
VF CS: 82%: █████████████████████████████████
Row 1, EU 3: 82%: █████████████████████████████████
Windowizer: 82%: █████████████████████████████████
Row 0, EU 3: 82%: █████████████████████████████████
ISC CS: 82%: █████████████████████████████████
Row 1, EU 2: 82%: █████████████████████████████████
Setup Engine: 82%: █████████████████████████████████
Row 0, EU 2: 82%: █████████████████████████████████
Row 1, EU 1: 82%: █████████████████████████████████
Row 1, EU 0: 82%: █████████████████████████████████
Row 0, EU 1: 82%: █████████████████████████████████
Map filter: 81%: ████████████████████████████████▌
Texture fetch: 79%: ███████████████████████████████▊
Bypass FIFO: 77%: ███████████████████████████████
Pixel shader: 75%: ██████████████████████████████▏
Texture decompress: 71%: ████████████████████████████▌
Filtering: 71%: ████████████████████████████▌
CL CS: 70%: ████████████████████████████▏
Sampler cache: 70%: ████████████████████████████▏
URB CS: 68%: ███████████████████████████▍
GS CS: 62%: █████████████████████████
VS0 CS: 49%: ███████████████████▊
Message Arbiter row 1: 32%: █████████████
EM1 CS CR: 13%: █████▍
SVDR CS CR: 7%: ███
SVSM CS CR: 5%: ██▏
SVTW CS CR: 0%: ▏
GW CS CR: 0%: ▏
UC1 CS: 0%: ▏
MAW CS CR: 0%: ▏
SVRR CS CR: 0%: ▏
SVRW CS CR: 0%: ▏
EM0 CS CR: 0%: ▏
MASM CS CR: 0%: ▏
SVDW CS CR: 0%: ▏
MASF CS CR: 0%: ▏
Projection and LOD: 0%: ▏
Dispatcher: 0%: ▏
For the shader case, I captured a GPU dump during execution. It is
attached (gzipped)
Is it possible the texture unit is involved in copying buffers? Or is it
just a case of mis-reporting what is active?
--
Peter Clifton
Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA
Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)
[-- Attachment #2: gpu_dump_texture_unit_busy.txt.gz --]
[-- Type: application/x-gzip, Size: 158631 bytes --]
[-- Attachment #3: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2010-10-07 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 17:55 intel_gpu_top decode Peter Clifton
2010-10-06 22:27 ` Eric Anholt
2010-10-07 11:41 ` Peter Clifton
2010-10-07 11:47 ` Peter Clifton
2010-10-07 12:55 ` Peter Clifton [this message]
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=1286456102.20269.31.camel@pcjc2lap \
--to=pcjc2@cam.ac.uk \
--cc=eric@anholt.net \
--cc=intel-gfx@lists.freedesktop.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.