[Mesa-dev] [PATCH] gallium/docs: fix definition of PIPE_QUERY_SO_STATISTICS
Marek Olšák
maraeo at gmail.com
Fri Mar 29 07:37:06 PDT 2013
Reviewed-by: Marek Olšák <maraeo at gmail.com>
Marek
On Fri, Mar 29, 2013 at 2:33 PM, Christoph Bumiller <
e0425955 at student.tuwien.ac.at> wrote:
> ---
> src/gallium/docs/source/context.rst | 8 +++++---
> 1 files changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/src/gallium/docs/source/context.rst
> b/src/gallium/docs/source/context.rst
> index 9e57930..2cc1848 100644
> --- a/src/gallium/docs/source/context.rst
> +++ b/src/gallium/docs/source/context.rst
> @@ -335,15 +335,17 @@ The result is a 64-bit integer specifying the timer
> resolution in Hz,
> followed by a boolean value indicating whether the timer has incremented.
>
> ``PIPE_QUERY_PRIMITIVES_GENERATED`` returns a 64-bit integer indicating
> -the number of primitives processed by the pipeline.
> +the number of primitives processed by the pipeline (regardless of whether
> +stream output is active or not).
>
> ``PIPE_QUERY_PRIMITIVES_EMITTED`` returns a 64-bit integer indicating
> the number of primitives written to stream output buffers.
>
> ``PIPE_QUERY_SO_STATISTICS`` returns 2 64-bit integers corresponding to
> -the results of
> +the result of
> ``PIPE_QUERY_PRIMITIVES_EMITTED`` and
> -``PIPE_QUERY_PRIMITIVES_GENERATED``, in this order.
> +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.
>
> ``PIPE_QUERY_SO_OVERFLOW_PREDICATE`` returns a boolean value indicating
> whether the stream output targets have overflowed as a result of the
> --
> 1.7.3.4
>
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/mesa-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20130329/c8fdafae/attachment-0001.html>
More information about the mesa-dev
mailing list