New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 762358 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 822346
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Evaluate avoiding a blit in VAAPI

Project Member Reported by dcasta...@chromium.org, Sep 6 2017

Issue description

We should soon get NV12 framebuffer support in 4.4 kernels for i915 where available.

Once we get NV12 framebuffer support in 4.4 and we land NV12 output for VAAPI decoders with crrev.com/c/569144, we'll be closer to a zero-copy hardware decoded video playback path on VAAPI devices.

The last copy that is happening during video playback with VAAPI is in VaapiVideoDecodeAccelerator::OutputPicture, during the DownloadFromSurface call, where a surface is blitted/converted from a vaSurface to an output picture.

If the format of the vaSurface produced by the decoder is the same as the one expected form the client of VaapiVideoDecodeAccelerator (likely with NV12), we might be able to skip that blit completely.

Kristian just commented out the extra blit to get a rough idea of power savings achievable and his estimate of best case power savings was in the order of .2 watts.

An additional benefit of removing the blit, not less important than the power saving, is that it is currently happening on the GPU main thread, sometimes stalling GPU compositing for big videos (crbug.com/717265).
 
Labels: videoshortlist
Cc: mcasas@chromium.org

Comment 3 by mcasas@chromium.org, Mar 15 2018

Mergedinto: 822346
Status: Duplicate (was: Available)
How can an issue be "available" and have an owner? Hmm.
Also, since this issue needs Chromium side code, it's not
an OS>Kernel one.

Sign in to add a comment