Chromium Code Reviews| Index: media/video/video_decode_accelerator.h |
| diff --git a/media/video/video_decode_accelerator.h b/media/video/video_decode_accelerator.h |
| index 7025a51cc82ae5db83b9befcc17fb0284005e5ff..499b24da9a6a68992a56d8080027a0b0036f7003 100644 |
| --- a/media/video/video_decode_accelerator.h |
| +++ b/media/video/video_decode_accelerator.h |
| @@ -132,6 +132,14 @@ class MEDIA_EXPORT VideoDecodeAccelerator { |
| // unconditionally, so make sure to drop all pointers to it! |
| virtual void Destroy() = 0; |
| + // Returns true if VDA::Decode and VDA::Client callbacks can run on the IO |
|
Ami GONE FROM CHROMIUM
2014/06/05 00:17:57
Please preface this comment with:
// GPU PROCESS
spang
2014/06/06 18:38:42
Done.
|
| + // thread. Otherwise they will run on the GPU child thread. The purpose of |
| + // running Decode on the IO thread is to reduce decode latency. Note Decode |
| + // should return as soon as possible and not block on the IO thread. Also, |
| + // PictureReady should be run on the child thread if a picture is delivered |
| + // the first time so it can be cleared. |
| + virtual bool CanDecodeOnIOThread() = 0; |
| + |
| protected: |
| // Do not delete directly; use Destroy() or own it with a scoped_ptr, which |
| // will Destroy() it properly by default. |