OpenCL essential calls
Yesterday I distilled a “hello world” C program which uses the OpenCL framework.
Let’s see the essential calls that that program makes.
Everything is in <OpenCL/opencl.h>
.
We make this available by compiling with -framework OpenCL
.
First our program finds our GPU,
using clGetDeviceIDs
.
(The Khronos site seems to be the canonical reference for OpenCL.)
The clGetDeviceIDs
call can find any and all available OpenCL devices,
but we ask it for just one GPU device.
We get back a cl_device_id
,
which is an opaque identifier type.
Next we create a context with clCreateContext
.
A context associates multiple devices, but we just give it one device: our GPU.
We get back a cl_context
.
We pass this context in to many future calls.
Next we create a command queue with clCreateCommandQueue
.
We pass in our GPU’s device ID:
all commands that we queue here will be processed by our GPU.
Next comes a set of three calls to compile our OpenCL kernel.
First we do clCreateProgramWithSource
, passing in the source code to our context.
Our OpenCL source looks like:
__kernel void square(__global float* input, __global float* output, const unsigned int count) {
int i = get_global_id(0);
if(i < count) { output[i] = input[i] * input[i]; }
}
This gives us a cl_program
.
Our program is not yet built;
to do that, we call clBuildProgram
.
Finally we extract a kernel from the program using clCreateKernel
,
passing the string "square"
.
A kernel is a function in a program.
We get the kernel for the function square
, as type cl_kernel
.
We don’t refer to the cl_program
again;
we only use it to get the cl_kernel
.
Next, we create two buffers - contiguous memory regions - with clCreateBuffer
.
One is an input buffer, the other an output buffer.
We’ll use these to communicate with the kernel function:
the buffers correspond to the input
and output
arguments to the kernel function.
These buffers are managed by OpenCL.
We specify the size of these buffers.
Both are set to 1024 float
s.
Next we write to the input buffer,
in preparation for calling the kernel.
We write to the input buffer with clEnqueueWriteBuffer
.
This command queues a command on the command queue we created earlier.
The clEnqueueWriteBuffer
command takes a buffer (our input buffer)
and a pointer to some data which we want to copy to the buffer.
We’ve pre-filled this buffer with the numbers 0..1023.
We specify that the clEnqueueWriteBuffer
call should be blocking.
This means the call will not return until the job has completed on the command queue.
Next we set the arguments to the kernel using clSetKernelArg
.
The kernel has three arguments, input
, output
and count
.
We refer to the arguments numerically: 0, 1, and 2.
We set input
to our input buffer (which we just filled),
and we set output
to the output buffer (which the kernel will fill when we call it).
Tagged .
Similar posts
More by Jim
What does the dot do in JavaScript?
foo.bar
, foo.bar()
, or foo.bar = baz
- what do they mean? A deep dive into prototypical inheritance and getters/setters. 2020-11-01
Smear phishing: a new Android vulnerability
Trick Android to display an SMS as coming from any contact. Convincing phishing vuln, but still unpatched. 2020-08-06
A probabilistic pub quiz for nerds
A “true or false” quiz where you respond with your confidence level, and the optimal strategy is to report your true belief. 2020-04-26
Time is running out to catch COVID-19
Simulation shows it’s rational to deliberately infect yourself with COVID-19 early on to get treatment, but after healthcare capacity is exceeded, it’s better to avoid infection. Includes interactive parameters and visualizations. 2020-03-14
The inception bar: a new phishing method
A new phishing technique that displays a fake URL bar in Chrome for mobile. A key innovation is the “scroll jail” that traps the user in a fake browser. 2019-04-27
The hacker hype cycle
I got started with simple web development, but because enamored with increasingly esoteric programming concepts, leading to a “trough of hipster technologies” before returning to more productive work. 2019-03-23
Project C-43: the lost origins of asymmetric crypto
Bob invents asymmetric cryptography by playing loud white noise to obscure Alice’s message, which he can cancel out but an eavesdropper cannot. This idea, published in 1944 by Walter Koenig Jr., is the forgotten origin of asymmetric crypto. 2019-02-16
How Hacker News stays interesting
Hacker News buried my post on conspiracy theories in my family due to overheated discussion, not censorship. Moderation keeps the site focused on interesting technical content. 2019-01-26
My parents are Flat-Earthers
For decades, my parents have been working up to Flat-Earther beliefs. From Egyptology to Jehovah’s Witnesses to theories that human built the Moon billions of years in the future. Surprisingly, it doesn’t affect their successful lives very much. For me, it’s a fun family pastime. 2019-01-20
The dots do matter: how to scam a Gmail user
Gmail’s “dots don’t matter” feature lets scammers create an account on, say, Netflix, with your email address but different dots. Results in convincing phishing emails. 2018-04-07
The sorry state of OpenSSL usability
OpenSSL’s inadequate documentation, confusing key formats, and deprecated interfaces make it difficult to use, despite its importance. 2017-12-02
I hate telephones
I hate telephones. Some rational reasons: lack of authentication, no spam filtering, forced synchronous communication. But also just a visceral fear. 2017-11-08
The Three Ts of Time, Thought and Typing: measuring cost on the web
Businesses often tout “free” services, but the real costs come in terms of time, thought, and typing required from users. Reducing these “Three Ts” is key to improving sign-up flows and increasing conversions. 2017-10-26
Granddad died today
Granddad died. The unspoken practice of death-by-dehydration in the NHS. The Liverpool Care Pathway. Assisted dying in the UK. The importance of planning in end-of-life care. 2017-05-19
How do I call a program in C, setting up standard pipes?
A C function to create a new process, set up its standard input/output/error pipes, and return a struct containing the process ID and pipe file descriptors. 2017-02-17
Your syntax highlighter is wrong
Syntax highlighters make value judgments about code. Most highlighters judge that comments are cruft, and try to hide them. Most diff viewers judge that code deletions are bad. 2014-05-11
Want to build a fantastic product using LLMs? I work at
Granola where we're building the future IDE for knowledge work. Come and work with us!
Read more or
get in touch! This page copyright James Fisher 2017. Content is not associated with my employer. Found an error? Edit this page.