Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

WebCL

From Wikipedia, the free encyclopedia
WebCL
DeveloperWebCL Working Group
Stable release
1.0 / March 19, 2014; 11 years ago (2014-03-19)[1]
Operating systemCross-platform
TypeAPI
Websitewww.khronos.org/webcl/
HTML
HTML and variants
HTML elements and attributes
Editing
Character encodings and language
Document and browser models
Client-side scripting and APIs
Graphics and Web3D technology
Comparisons

WebCL (Web Computing Language) is aJavaScript binding toOpenCL forheterogeneousparallel computing within any compatibleweb browser without the use ofplug-ins, first announced in March 2011. It is developed on similar grounds as OpenCL and is considered as a browser version of the latter. Primarily, WebCL allows web applications to actualize speed with multi-coreCPUs andGPUs. With the growing popularity of applications that needparallel processing like image editing,augmented reality applications and sophisticated gaming, it has become more important to improve the computational speed. With these background reasons, a non-profit Khronos Group[2] designed and developed WebCL, which is a Javascript binding to OpenCL with a portable kernel programming, enabling parallel computing on web browsers, across a wide range of devices. In short, WebCL consists of two parts, one being Kernel programming, which runs on the processors (devices) and the other being JavaScript, which binds the web application to OpenCL. The completed and ratified specification for WebCL 1.0 was released on March 19, 2014.[2]

Implementation

[edit]

Currently,[when?] no browsers natively support WebCL. However, non-native add-ons are used to implement WebCL. For example,Nokia developed a WebCL extension.[3]Mozilla does not plan to implement WebCL in favor ofWebGLCompute Shaders, which were in turn scrapped in favor ofWebGPU.

WebCL working draft

[edit]

Example C code

[edit]

The basic unit of a parallel program iskernel. A kernel is any parallelizable task used to perform a specific job. More often functions can be realized as kernels. A program can be composed of one or more kernels. In order to realize a kernel, it is essential that a task is parallelizable.Data dependencies and order of execution play a vital role in producing efficient parallelized algorithms. A simple example can be thought of the case ofloop unrolling performed by C compilers, where a statement like:

for(i=0;i<3;i++)c[i]=a[i]+b[i];

can be unrolled into:

c[0]=a[0]+b[0];c[1]=a[1]+b[1];c[2]=a[2]+b[2];

Above statements can be parallelized and can be made to run simultaneously. A kernel follows a similar approach where only the snapshot of the ith iteration is captured inside kernel.Rewriting the above code using a kernel:

__kerneladd(__globalfloat*a,__globalfloat*b,__globalfloat*c){inti=get_global_id(0);if(i<3)c[i]=a[i]+b[i];}

Running a WebCL application involves the following steps:

  1. Allow access to devices and provide context
  2. Hand over the kernel to a device
  3. Cause the device to execute the kernel
  4. Retrieve results from the device
  5. Use the data inside JavaScript

Further details about the same can be found at[5]

Exceptions List

[edit]

WebCL, being a JavaScript based implementation, doesn't return an error code when errors occur. Instead, it throws an exception such asOUT_OF_RESOURCES,OUT_OF_HOST_MEMORY, or the WebCL-specificWEBCL_IMPLEMENTATION_FAILURE.[6] The exception object describes the machine-readable name and human-readable message describing the error. The syntax is as follows:

exceptionWebCLException:DOMException{DOMStringname;// A string representation of the numeric error code, e.g. "INVALID_VALUE"DOMString?message;// An implementation-specific description of what caused the exception};

From the code above, it can be observed that the message field can be a NULL value. Other exceptions include:

  1. INVALID_OPERATION – if the blocking form of this function is called from aWebCLCallback
  2. INVALID_VALUE – ifeventWaitList is empty
  3. INVALID_CONTEXT – if events specified ineventWaitList do not belong to the same context
  4. INVALID_DEVICE_TYPE – ifdeviceType is given, but is not one of the valid enumerated values
  5. DEVICE_NOT_FOUND – if there is noWebCLDevice available that matches the givendeviceType

More information on exceptions can be found in the specs document.[6]

There is another exception that is raised upon trying to call an object that is ‘released’. On using the release method, the object doesn't get deleted permanently but it frees the resources associated with that object. In order to avoid this exception,releaseAll method can be used, which not only frees the resources but also deletes all the associated objects created.

Security

[edit]

WebCL, being an open-ended software developed for web applications, has lots of scope for vulnerabilities in the design and development fields too. This forced the developers working on WebCL to give security the utmost importance. Few concerns that were addressed are:

  1. Out-of-bounds Memory Access: This occurs by accessing the memory locations, outside the allocated space. An attacker can rewrite or erase all the important data stored in those memory locations. Whenever there arises such a case, an error must be generated at the compile time, and zero must be returned at run-time, not letting the program override the memory. A project WebCL Validator,[7] was initiated by the Khronos Group (developers) on handling this vulnerability.
  2. Memory Initialization: This is done to prevent the applications to access the memory locations of previous applications. WebCL ensures that this doesn't happen by initializing all the buffers, variables used to zero before it runs the current application. OpenCL 1.2 has an extension ‘cl_khr_initialize_memory’, which enables this.[6]
  3. Denial of Service: The most common attack on web applications cannot be eliminated by WebCL or the browser. OpenCL can be provided with watchdog timers and pre-emptive multitasking, which can be used by WebCL in order to detect and terminate the contexts that are taking too long or consume lot of resources. There is an extension of OpenCL 1.2 ‘cl_khr_terminate_context’ like for the previous one, which enables to terminate the process that might cause a denial of service attack.[6]

Related browser bugs

[edit]

See also

[edit]

References

[edit]
  1. ^"Khronos Releases WebCL 1.0 Specification". 19 March 2014.
  2. ^ab"Khronos Releases WebCL 1.0 Specification". Khronos Group. 19 March 2014. RetrievedMarch 19, 2014.
  3. ^"WebCL". Nokia Research. Archived fromthe original on May 10, 2012. RetrievedMay 6, 2012.
  4. ^"Crosswalk - WebCL Overview". Archived fromthe original on 2017-02-01. Retrieved2017-02-01.
  5. ^"Accelerating web applications with OpenCL".IBM.
  6. ^abcd"WebCL Specification".www.khronos.org. Retrieved2016-09-14.
  7. ^"KhronosGroup/webcl-validator".GitHub. Retrieved2016-09-14.

External links

[edit]
Khronos Group Standards
Active
Inactive
Protocols
Server APIs
Apache modules
Topics
Browser APIs
Web APIs
WHATWG
W3C
Khronos
Others
Topics
Related topics
Retrieved from "https://en.wikipedia.org/w/index.php?title=WebCL&oldid=1320519422"
Categories:
Hidden categories:

[8]ページ先頭

©2009-2025 Movatter.jp