How to use 2 OpenCL runtimes

7
votes

I want to use 2 OpenCL runtimes in one system together (in my case AMD and Nvidia, but the question is pretty generic).

I know that I can compile my program with any SDK. But when running the program, I need to provide libOpenCL.so. How can I provide the libs of both runtimes so that I see 3 devices (AMD CPU, AMD GPU, Nvidia GPU) in my OpenCL program?

I know that it must be possible somehow, but I didn't find a description on how to do it for linux, yet.

Thanks a lot, Tomas

4
opencl
An application cannot load 2 libraries which exports the same functions, but you can run the same app twice, each time loading different libraries: LD_LIBRARY_PATH=/usr/lib64/OpenCL/vendors/intel; ./app_to_run LD_LIBRARY_PATH=/usr/lib64/OpenCL/vendors/amd; ./app_to_run This is what you want ? - Sacx
Cool, that would be one solution. But I really want to use it in one application. With your solution I would have to start 2 apps for each runtime and then connect the apps somehow to use both runtimes in one program... I really hope there is a easier way!! - Tomas

4 Answers

4
votes

The Smith and Thomas answers are correct; this is just expanding on that information: When you enumerate the OpenCL platforms, you'll get one for each installed driver. Within each platform you enumerate the devices. The AMD and Intel drivers also expose CPU devices. So on a fully populated machines, you might see an AMD platform (with CPU and GPU devices), an NVIDIA platform (with GPU device), and an Intel platform (with CPU and GPU devices). Your code creates a context on whichever devices you want to use, and one or more command queues to feed them work. You can keep them all busy working on things, but you can only share data buffers between devices from the same platform. To share data across platforms, it must hit CPU memory in between.

6
votes

You're not thinking of it right. SDK's are not provided by the application, and are not needed for running a compiled program. OpenCL runtimes are provided by the client system, and that's what's giving your program platforms and devices to use in clGetPlatformIDs and clGetDeviceIDs.

If the user does not have an Nvidia graphics card, you are simply not going to be able to use an Nvidia platform and device on his system, because he doesn't have the Nvidia OpenCL runtime or hardware.

All different OpenCL SDK's provide you are vendor-specific extensions, which are then understood by the vendor runtime.

5
votes

The Khronos OpenCL working group defined a ICD layer (installable client driver) that allows multiple vendor drivers to be installed on the system. The application accesses the vendor drivers through the ICD layer. For more details see cl_khr_icd.txt.

2
votes

In regards to running on multiple OpenCL devices at the same time. If you want to run on multiple devices create a separate context for each device/vendor and run each one in a separate thread. For example I have a GTX 590. This shows up as two GTX 590 devices. I also have the Intel i7 processor. I create three contexts: two for the 590 devices and one for the CPU and run each context/device in three threads using SDL_CreateThread (pthreads works well as well). You have to weight the number of jobs for each device proportional to their "speed" if you want to get good results. For example 45% for each GTX 590 and 10% for the CPU. The best weights to use depend on the application.