[Webkit-unassigned] [Bug 70099] OpenCL implementation of W3C Filter Effects Master Bug

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=70099


Vangelis Kokkevis <vangelis at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |senorblanco at chromium.org,
                   |                            |vangelis at chromium.org




--- Comment #6 from Vangelis Kokkevis <vangelis at chromium.org>  2011-10-17 09:42:13 PST ---
One more data point:

It's unlikely that Chrome will be able to use an OpenCL implementation of filters, at least not without lots of additional work. The reason is that Chrome's security model prevents WebKit from directly accessing the GPU. All graphics calls are proxied over to a separate process for validation and execution. The proxying mechanism is hidden behind our GraphicsContext3D implementation so any code using GC3D can take advantage of it. Adding support for executing sufficiently validated OpenCL code on a secondary process won't be trivial.

For this and all the reasons that Chris mentioned, I would also favor implementing filters using GC3D and GLSL instead of OpenCL.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.