Clear old verified flush IDs when doing OrderingBarrier.

Clear old verified flush IDs when doing OrderingBarrier.

If a command buffer generates sync tokens but doesn't validate them
(letting a different command buffer in the same stream do that), then
its queue of unverified flush ids will grow without bound. It can clear
them out with little overhead by checking which ones are verified after
every GpuChannelHost::OrderingBarrier call.

BUG=635051
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Committed: https://crrev.com/c5faeccf26cc5e05407c6375231aef4e736138f9
Cr-Commit-Position: refs/heads/master@{#410840}

[jbauman, 2016-08-05 21:44:41]

Description was changed from

==========
Clear old verified flush IDs when doing OrderingBarrier.

If a command buffer generates sync tokens but doesn't validate them
(letting a different command buffer in the same stream do that), then
its queue of unverified flush ids will grow without bound. It can clear
them out with little overhead by checking which ones are verified after
every GpuChannelHost::OrderingBarrier call.

BUG=635051
==========

to

==========
Clear old verified flush IDs when doing OrderingBarrier.

If a command buffer generates sync tokens but doesn't validate them
(letting a different command buffer in the same stream do that), then
its queue of unverified flush ids will grow without bound. It can clear
them out with little overhead by checking which ones are verified after
every GpuChannelHost::OrderingBarrier call.

BUG=635051
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[jbauman, 2016-08-05 21:44:47]

The CQ bit was checked by jbauman@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-05 21:45:11]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[jbauman, 2016-08-05 22:47:10]

jbauman@chromium.org changed reviewers:
+ piman@chromium.org

[commit-bot: I haz the power, 2016-08-05 22:54:15]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-05 22:54:17]

Dry run: This issue passed the CQ dry run.

[piman, 2016-08-08 15:25:07]

lgtm

[jbauman, 2016-08-09 08:14:58]

The CQ bit was checked by jbauman@chromium.org

[commit-bot: I haz the power, 2016-08-09 08:15:26]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-09 09:21:40]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-09 09:21:41]

Try jobs failed on following builders:
  win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[jbauman, 2016-08-09 19:23:12]

The CQ bit was checked by jbauman@chromium.org

[commit-bot: I haz the power, 2016-08-09 19:24:22]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-09 21:50:47]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-09 21:52:12]

Description was changed from

==========
Clear old verified flush IDs when doing OrderingBarrier.

If a command buffer generates sync tokens but doesn't validate them
(letting a different command buffer in the same stream do that), then
its queue of unverified flush ids will grow without bound. It can clear
them out with little overhead by checking which ones are verified after
every GpuChannelHost::OrderingBarrier call.

BUG=635051
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

to

==========
Clear old verified flush IDs when doing OrderingBarrier.

If a command buffer generates sync tokens but doesn't validate them
(letting a different command buffer in the same stream do that), then
its queue of unverified flush ids will grow without bound. It can clear
them out with little overhead by checking which ones are verified after
every GpuChannelHost::OrderingBarrier call.

BUG=635051
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Committed: https://crrev.com/c5faeccf26cc5e05407c6375231aef4e736138f9
Cr-Commit-Position: refs/heads/master@{#410840}
==========

[commit-bot: I haz the power, 2016-08-09 21:52:13]

Patchset 1 (id:??) landed as
https://crrev.com/c5faeccf26cc5e05407c6375231aef4e736138f9
Cr-Commit-Position: refs/heads/master@{#410840}