I have two arrays, a and b, and I would like to compute the “min convolution” to produce result c. Simple pseudo code looks like the following:
for i = 0 to size(a)+size(b)
c[i] = inf
for j = 0 to size(a)
if (i - j >= 0) and (i - j < size(b))
c[i] = min(c[i], a[j] + b[i-j])
(edit: changed loops to start at 0 instead of 1)
If the min were instead a sum, we could use a Fast Fourier Transform (FFT), but in the min case, there is no such analog. Instead, I’d like to make this simple algorithm as fast as possible by using a GPU (CUDA). I’d be happy to find existing code that does this (or code that implements the sum case without FFTs, so that I could adapt it for my purposes), but my search so far hasn’t turned up any good results. My use case will involve a’s and b’s that are of size between 1,000 and 100,000.
Questions:
-
Does code to do this efficiently already exist?
-
If I am going to implement this myself, structurally, how should the CUDA kernel look so as to maximize efficiency? I’ve tried a simple solution where each c[i] is computed by a separate thread, but this doesn’t seem like the best way. Any tips in terms of how to set up thread block structure and memory access patterns?
An alternative which might be useful for large
aandbwould be to use a block per output entry inc. Using a block allows for memory coalescing, which will be important in what is a memory bandwidth limited operation, and a fairly efficient shared memory reduction can be used to combine per thread partial results into a final per block result. Probably the best strategy is to launch as many blocks per MP as will run concurrently and have each block emit multiple output points. This eliminates some of the scheduling overheads associated with launching and retiring many blocks with relatively low total instruction counts.An example of how this might be done:
[disclaimer: not tested or benchmarked, use at own risk]
This is single precision floating point, but the same idea should work for double precision floating point. For integer, you would need to replace the C99
INFINITYmacro with something likeINT_MAXorLONG_MAX, but the principle remains the same otherwise.