Welcome to the oneAPI channel.
So what is oneAPI?
Why do you need it ? And why do you care
Here is a simple scenario that happens every day.
You watch your favorite TV-Show or play a game on your wide-screen TV.
Then, you continue from your living room on your tablet device
And then you may finish watching the rest of the show on your mobile device on the train
to work or anywhere..
We are used to such multi-device continuum experience and we expect nothing less…
And there are many such examples, think about a street camera communicating
through multiple compute nodes all the way to the city command center to report an accident,
Or any other edge to cloud application..
These are amazing times in terms of the diversity of workloads we are dealing with
..they all require a diverse set of architectures
And we see an explosion of devices and silicon accelerators
I want to use the power of them all,
I want to be able to run object recognition on a 1W drone or process a 1000 video channels
in the cloud But each of these accelerators has his own
libraries, tools or a unique programming model that
Makes it challenging to reuse code and be productive across all these architectures.
In order for developers to make such a continuum experience happen with the best performance
sometimes, almost the same code has to be written and re-written in Java, C++, Python
and maybe other languages, Compiled on multiple operating systems, sometimes
using totally different APIs, libraries, SDKs…
A lot of overhead instead of focusing on algorithms and innovations."
The bold vision of oneAPI is to have a cross-architecture, cross vendors SW portability while providing
you all the performance you need.
So no matter what devices and accelerators your system might have
Or what languages and libraries each of these devices is using
Middleware or frameworks applications and workloads
oneAPI is bridging, abstracting and bringing all these devices to a common ground
Where memory spaces could be shared, code could be ported and re-used,
and tools could work across architectures
The industry-wide spec of oneAPI defines a low level abstraction layer inside the software
stack
And you can use the set of optimized libraries for various domains.
For example, oneDNN the deep neural network library or oneMKL, the Math Kernel Library
video processing library And more
In addition, for cross-architecture direct programming the Data Parallel C++ or DPC++
language is included
It is built on open standards and specifications and we’ll have a few dedicated videos to
walk you through the details of those
The Intel implementation of oneAPI includes many additional libraries, compilers, and
analyzers.
It is arranged in toolkits for specific application domains, and can be downloaded in many ways
or used remotely on the Intel DevCloud
The oneAPI spec is being discussed and formed by many partners in the industry,
So everyone can read the spec and come up with his specific implementation..
all the details in the next video..
In the coming videos you will find all the information about the oneAPI spec, the libraries,
the toolkits, all the concepts, the resources available
and practical actionable information and code samples to get you started
Subscribe to the oneAPI channel We’ll make sure you have all the information
See you there