diff options
author | Roland Scheidegger <[email protected]> | 2013-08-23 23:08:43 +0200 |
---|---|---|
committer | Roland Scheidegger <[email protected]> | 2013-08-27 16:59:39 +0200 |
commit | bd3909f265908e30ef0e569fab57e9a042750b3a (patch) | |
tree | c98086d22693a9eab4900a7df27046573b831e0e /src/gallium/docs | |
parent | aff2ecf09a92eb79eef560f17d77badf69782e7c (diff) |
draw: clean up setting stream out information a bit
In particular noone is interested in the vertex count, so drop that,
and also drop the duplicated num_primitives_generated /
so.primitives_storage_needed variables in drivers. I am unable for now to figure
out if primitives_storage_needed in SO stats (used for d3d10) should
increase if SO is disabled, though the equivalent num_primitives_generated
used for OpenGL definitely should increase. In any case we were only counting
when SO is active both in softpipe and llvmpipe anyway so don't pretend there's
an independent num_primitives_generated counter which would count always.
(This means the PIPE_QUERY_PRIMITIVES_GENERATED count will still be wrong just
as before, should eventually fix this by doing either separate counting for this
query or adjust the code so it always counts this even if SO is inactive depending
on what's correct for d3d10.)
Reviewed-by: Brian Paul <[email protected]>
Diffstat (limited to 'src/gallium/docs')
-rw-r--r-- | src/gallium/docs/source/context.rst | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/gallium/docs/source/context.rst b/src/gallium/docs/source/context.rst index bfd58a48d9e..95f6b228fa2 100644 --- a/src/gallium/docs/source/context.rst +++ b/src/gallium/docs/source/context.rst @@ -350,6 +350,8 @@ the result of ``PIPE_QUERY_PRIMITIVES_EMITTED`` and the number of primitives that would have been written to stream output buffers if they had infinite space available (primitives_storage_needed), in this order. +XXX the 2nd value is equivalent to ``PIPE_QUERY_PRIMITIVES_GENERATED`` but it is +unclear if it should be increased if stream output is not active. ``PIPE_QUERY_SO_OVERFLOW_PREDICATE`` returns a boolean value indicating whether the stream output targets have overflowed as a result of the |