3 ms·
> They did not include the time it took to transfer the input file from memory to the GPU Fair point, it's more support for this HN post[2] making the case for
by ben509 7y ago
> They did not include the time it took to transfer the input file from memory to the GPU
Fair point, it's more support for this HN post[2] making the case for memory-mapping files to GPU.
> This is a neat project, but there is a reason we are not using the GPU for regex matching.
I think it's more interesting that it's a general facility for running automata on a GPU, as it's opening up the universe of things that can be accelerated by a GPU. For instance, Numba[1] is a library to run arbitrary math code, and it has a feature for generating code to run on the GPU.
[1]: http://numba.pydata.org/numba-doc/latest/cuda/index.html http://numba.pydata.org/numba-doc/latest/cuda/index.html
[2]: https://news.ycombinator.com/item?id=11892030 https://news.ycombinator.com/item?id=11892030
- shaklee3 7y agoCUDA already has this built in (for many years) using UVM. That won't take away the bottleneck of the transfer, but it does make it transparent to the user by handling all the paging/copies.
- mzs 7y agoI thought that just made GPU memory map equal to CPUs' and you need much for VM (like paging).