commit 9c952f71fb7cd97ad99f6707002050de00a63f67
author Miguel Casas <mcasas@chromium.org> Wed Feb 06 23:21:34 2019
committer Commit Bot <commit-bot@chromium.org> Wed Feb 06 23:21:34 2019
tree e3837e84649a7569e3e2382ddc93b37ab44c7be3
parent e005fff9c838a13ff1402b01617adca691187a6b

VaVDA: split kReduced and kSuperReduced modes

H264 GetNumReferenceFrames() was increased by 1 [1] for all platforms to
circumvent a limitation during introduction of the kReduced mode; this
CL:
- Renames VaVDA::BufferAllocationMode::kReduced to kSuperReduced.
- Takes that +1 out of h264_decoder
- Introduces kReduced to represent this H264 case where we +1 the
  amount of media pipeline frames allocated.

Note that this CL doesn't change ToT: there's an extra allocation
in the # codec reference frames _and_ in the amount of pipeline
buffers.

Test results ToT: https://pastebin.com/YG1Tcgya
With this change: https://pastebin.com/JgER07id and
https://paste.googleplex.com/5473272024006656 (2nd round) - similar.

This way, we can have all buffer amount calculations in one place,
specially with a view to introducing kReduced for platforms < SkyLake.

[1] https://cs.chromium.org/chromium/src/media/gpu/h264_decoder.cc?dr=C&sq=package:chromium&g=0&l=1428

TBR=hiroh@chromium.org (bc of
  http://crrev.com/c/1455302#message-3083834c541894c42a630b7fd73b6cd5095ce67e)

Test: tast run DEVICE_IP video.PlaybackPerfH2642160P60FPS on a SkyLake device (cave)
Bug: 912295, 920510
Change-Id: Ice286b1bd4db21f353d86cb9c65467e1322963be
Reviewed-on: https://chromium-review.googlesource.com/c/1455302
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#629774}