Want to add OpenCL/WebCL support into Blink and Chromium.

Showing 1-5 of 5 messages
Want to add OpenCL/WebCL support into Blink and Chromium. Peixuan Zhang 4/6/13 7:09 PM
Hello All,
     Is there any plan of adding OpenCL/WebCL support into Blink? I know the biggest problem is to bypass the sandbox in Chromium, but I think Browsers need to support WebCL in the further. Is there any development plan? And if our team want to add such support into Blink or Chromium, is there any suggestion about how to do it?
     Our team has completed some code using OpenCL and want to contribute to Chromium or Blink, but now Chromium doesn't support OpenCL, so we want to do some work about OpenCL/WebCL support in Chromium/Blink. I want some suggestion, Thanks a lot.
Re: [blink-dev] Want to add OpenCL/WebCL support into Blink and Chromium. Adam Barth 4/7/13 2:56 PM
Hi Peixuan,

On Sat, Apr 6, 2013 at 7:09 PM, Peixuan Zhang <zhangpe...@gmail.com> wrote:
     Is there any plan of adding OpenCL/WebCL support into Blink? I know the biggest problem is to bypass the sandbox in Chromium, but I think Browsers need to support WebCL in the further. Is there any development plan?

We have no current plans to implement OpenCL/WebCL.
 
And if our team want to add such support into Blink or Chromium, is there any suggestion about how to do it?

You can find the guidelines for adding new features to Blink on the project page:


In particular, we're interested in the feature's progress on the standards track, implementation interest from other browser vendors, and API footprint.
 
     Our team has completed some code using OpenCL and want to contribute to Chromium or Blink, but now Chromium doesn't support OpenCL, so we want to do some work about OpenCL/WebCL support in Chromium/Blink. I want some suggestion, Thanks a lot.

Thanks for your interest in contributing to Blink.  The project is very new, and most of our efforts are focused on cleanup, refactoring, and infrastructure at the moment.  That doesn't mean we aren't taking on new features, just that we're being conservative at the moment.

If you're interested in contributing to Blink, I'd recommend starting off in one of the areas we're currently focused on, namely cleanup and refactoring.  If you'd like some more concrete advice, feel free to ask.

Thanks!
Adam

Re: [blink-dev] Want to add OpenCL/WebCL support into Blink and Chromium. Peter Beverloo 4/8/13 5:31 AM
On Sun, Apr 7, 2013 at 10:56 PM, Adam Barth <aba...@chromium.org> wrote:
Hi Peixuan,

On Sat, Apr 6, 2013 at 7:09 PM, Peixuan Zhang <zhangpe...@gmail.com> wrote:
     Is there any plan of adding OpenCL/WebCL support into Blink? I know the biggest problem is to bypass the sandbox in Chromium, but I think Browsers need to support WebCL in the further. Is there any development plan?

We have no current plans to implement OpenCL/WebCL.

WebCL already has an implementation in Blink, though it is disabled through a compile time flag.  No plumbing through the public API has been done to make this work for Chromium, so I suspect Peixuan Zhang's interest is in enabling the compile time flag and implementing it in Chromium.

I personally have doubts about the API itself; we should definitely do an API Review if we decide to pursue wiring up this feature.

Peter

 
And if our team want to add such support into Blink or Chromium, is there any suggestion about how to do it?

You can find the guidelines for adding new features to Blink on the project page:


In particular, we're interested in the feature's progress on the standards track, implementation interest from other browser vendors, and API footprint.
 
     Our team has completed some code using OpenCL and want to contribute to Chromium or Blink, but now Chromium doesn't support OpenCL, so we want to do some work about OpenCL/WebCL support in Chromium/Blink. I want some suggestion, Thanks a lot.

Thanks for your interest in contributing to Blink.  The project is very new, and most of our efforts are focused on cleanup, refactoring, and infrastructure at the moment.  That doesn't mean we aren't taking on new features, just that we're being conservative at the moment.

If you're interested in contributing to Blink, I'd recommend starting off in one of the areas we're currently focused on, namely cleanup and refactoring.  If you'd like some more concrete advice, feel free to ask.

Thanks!
Adam


Re: [blink-dev] Want to add OpenCL/WebCL support into Blink and Chromium. Stephen Chenney 4/8/13 7:25 AM
See my comments on the other post.

In short, we'll be removing the OpenCL defines and code from Blink in the short term because it is not designed in a way that is suitable for Chrome.

Stephen.--
Stephen Chenney | Software Engineer | sche...@google.com | 404-314-1809
Re: [blink-dev] Want to add OpenCL/WebCL support into Blink and Chromium. Justin 4/8/13 9:50 AM
On Mon, Apr 8, 2013 at 7:25 AM, Stephen Chenney <sche...@google.com> wrote:
See my comments on the other post.

In short, we'll be removing the OpenCL defines and code from Blink in the short term because it is not designed in a way that is suitable for Chrome.


Just to expand on Stephen's point, our multi-process split and sandbox make it impossible to use OpenCL directly from inside a renderer. So, if we did decide to support WebCL in Blink (which is another complicated security question) we'd need to write an entirely new implementation that plumbed all of the OpenCL support through to an appropriate process (probably the GPU process). As such, Stephen is entirely correct that the WebKit OpenCL implementation is just dead code that we need to remove.

-j