MJPEG acceleration for video capture using VAAPI

content/browser/renderer_host/media/video_capture_buffer_pool.cc

Index: content/browser/renderer_host/media/video_capture_buffer_pool.cc
diff --git a/content/browser/renderer_host/media/video_capture_buffer_pool.cc b/content/browser/renderer_host/media/video_capture_buffer_pool.cc
index f583a94adaa638396431ecda7017aa787d99aaa2..900240b61901173934781ebc96875b13aef1334d 100644
--- a/content/browser/renderer_host/media/video_capture_buffer_pool.cc
+++ b/content/browser/renderer_host/media/video_capture_buffer_pool.cc
@@ -168,4 +168,12 @@ VideoCaptureBufferPool::Buffer* VideoCaptureBufferPool::GetBuffer(
   return it->second;
 }
 
+base::SharedMemoryHandle VideoCaptureBufferPool::GetBufferSharedMemory(
+    int buffer_id) {

[wuchengli, 2015/03/23 06:30:14]

Need to acquire |lock_|.

Or how about merging this with GetBufferInfo and store the handle in
media::VideoCaptureDevice::Client::Buffer?

[mcasas, 2015/03/23 19:29:50]

For another purpose I'm about to start adding a 
VideoCaptureDevice::Client::GetHandle(), which would
be a shared memory fd or a dma-buf fd depending on
the platform capabilities etc. 

Depending on the platform, the BufferPool Buffers might
not be backed by SharedMemory.

[kcwu, 2015/03/30 18:12:14]

Did you mean VideoCaptureDevice::Client::Buffer::GetHandle() ?
Now I'm adding VideoCaptureDevice::Client::Buffer::handle(), which returns
base::SharedMemoryHandle, based on wuchengli's suggestion. What should I do to
fit your plan?

[kcwu, 2015/03/30 18:12:14]

Done.

+  BufferMap::iterator it = buffers_.find(buffer_id);
+  if (it == buffers_.end())
+    return base::SharedMemory::NULLHandle();
+  return it->second->shared_memory.handle();
+}
+
 }  // namespace content