oneAPI is an open, free, and standards-based programming system that provides portability and performance across accelerators and generations of hardware. oneAPI consists of a language and libraries for creating parallel applications:
DPC++: oneAPI’s core language for programming accelerators and multiprocessors. DPCPP allows developers to reuse code across hardware targets (CPUs and accelerators such as GPUs and FPGAs) and tune for a specific architecture
oneDPL: A companion to the DPC++ Compiler for programming oneAPI devices with APIs from C++ standard library, Parallel STL, and extensions.
oneDNN: High performance implementations of primitives for deep learning frameworks
oneCCL: Communication primitives for scaling deep learning frameworks across multiple devices
Level Zero: System interface for oneAPI languages and libraries
oneDAL: Algorithms for accelerated data science
oneTBB: Library for adding thread-based parallelism to complex applications on multiprocessors
oneVPL: Algorithms for accelerated video processing
oneMKL: High performance math routines for science, engineering, and financial applications
oneAPI simplifies software development by providing the same languages and programming models across accelerator architectures. In this section, we introduce the programming model.
Parallel application development is a combination of API programming, where the parallel algorithm is hidden behind an API provided by the system, and direct programming, where the application programmer writes the parallel algorithm.
When using API programming, a developer implements performance critical sections of the program with library calls. Well-defined and mature problem domains have high-performance solutions packaged as libraries. oneAPI defines a set of APIs for the most used data parallel domains, and oneAPI platforms provide library implementations across a variety of accelerators. Where possible, the API is based on established standards like BLAS. API programming enables a programmer to attain high performance across a diverse set of accelerators with minimal coding & tuning.
Some problem domains are not well suited to API programming because no standard solution exists or because solutions require a level of customization that cannot be easily implemented in a library. In this case, a developer uses direct programming and must explicitly code the parallel algorithm. oneAPI’s programming model is based on data parallelism, where the same computation is performed on each data element, and parallelism of the application scales as the data scales. By allowing the programmer to directly express parallelism, data parallel algorithms make it possible to productively create highly efficient algorithms for parallel architectures.
Data parallel algorithms are used for many of the most computationally demanding problems including scientific computing, artificial intelligence, and visualization. Data parallel algorithms can be efficiently mapped to a diverse set of architectures: multi-core CPUs, GPUs, systolic arrays, and FPGAs.
The expected audience for this specification includes: application developers, middleware developers, system software providers, and hardware providers. As a contributor to this specification, you will shape the accelerator software ecosystem. A productive and high performing system must take into account the constraints at all levels of the software stack. As a user of this document, you can ensure that your components will inter-operate with applications and system software for the oneAPI platform.
Goals of the Specification¶
oneAPI seeks to provide:
Source-level compatibility: oneAPI applications and middleware port to a conformant oneAPI platform through recompilation and re-tuning.
Performance transparency: API’s and language construct allow the programmer enough control over the mapping to hardware to create an efficient solution
Software stack portability: Platform providers can port a oneAPI software stack by implementing the oneAPI Level Zero interface.
This specification uses the definition of must, must not, required, and so on specified in RFC 2119.
This specification is a continuation of Intel’s decades-long history of working with standards groups and industry/academia initiatives such as The Khronos Group, to create and define specifications in an open and fair process to achieve interoperability and interchangeability. oneAPI is intended to be an open specification and we encourage you to help us make it better. Your feedback is optional, but to enable Intel to incorporate any feedback you may provide to this specification, and to further upstream your feedback to other standards bodies, including The Khronos Group SYCL specification, please submit your feedback under the terms and conditions below. Any contribution of your feedback to the oneAPI Specification does not prohibit you from also contributing your feedback directly to other standard bodies, including The Khronos Group under their respective submission policies.
Contribute to the oneAPI Specification by opening issues in the oneAPI Specification GitHub repository.
Sign your work¶
Please include a signed-off-by tag in every contribution of your feedback. By including a signed-off-by tag, you agree that: (a) you have a right to license your feedback to Intel; (b) Intel will be free to use, disclose, reproduce, modify, license, or otherwise distribute your feedback at its sole discretion without any obligations or restrictions of any kind, including without limitation, intellectual property rights or licensing obligations; and (c) your feedback will be public and that a record of your feedback may be maintained indefinitely.
If you agree to the above, every contribution of your feedback must include the following line using your real name and email address: Signed-off-by: Joe Smith email@example.com