[surfaces] use DEFAULT_MAX_FRAMES_PENDING if OutputSurface doesn't specify it.

[surfaces] use DEFAULT_MAX_FRAMES_PENDING if OutputSurface doesn't specify it.

To match LTHI, change the max frames pending calculation to output DEFAULT_MAX_FRAMES_PENDING if the output surface reports 0.

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

[jbauman, 2015-01-29 21:11:39]

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

[jamesr, 2015-01-29 21:21:53]

The patch description says one thing but the code says another - isn't this
doing something more like "use DEFAULT_... if output_surface does not specify a
max"?

We should probably always end up with a max_frames_pending of 1, just like
ubercomp.

[jamesr, 2015-01-29 21:22:17]

Or to put it another way DEFAULT_MAX_.. being 2 isn't a concern of this bit of
code.

[jbauman, 2015-01-29 21:25:14]

On 2015/01/29 21:21:53, jamesr wrote:
> The patch description says one thing but the code says another - isn't this
> doing something more like "use DEFAULT_... if output_surface does not specify
a
> max"?
> 
> We should probably always end up with a max_frames_pending of 1, just like
> ubercomp.

Ok, changed the patch description.

[jamesr, 2015-01-29 21:29:08]

lgtm

[jbauman, 2015-01-29 21:29:32]

The CQ bit was checked by jbauman@chromium.org

[commit-bot: I haz the power, 2015-01-29 21:30:14]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/885933002/1

[commit-bot: I haz the power, 2015-01-29 21:59:04]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-01-29 21:59:54]

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