Paul Berry <stereotype...@gmail.com> writes: > Normally when submitting the first batch buffer after a flush, we > check whether the GPU has completed processing of the first batch > buffer of the previous frame. If it hasn't, we wait for it to finish > before submitting any more batches. This prevents GPU-heavy and > CPU-light applications from racing too far ahead of the current frame, > but at the expense of possibly lower frame rates. Sometimes when > benchmarking we want to disable this mechanism. > > This patch adds the driconf option "disable_throttling" to disable the > throttling mechanism.
We often do our driver-specific options inside of intel_screen.c, but I suppose this way someone could potentially translate it. Reviewed-by: Eric Anholt <e...@anholt.net> Have you found any interesting cases where this is a problem?
pgpb2GU6r28Fg.pgp
Description: PGP signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
