-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[QST] Is it available BITCOMP decompression for cpu? #104
Comments
Andrea, Bitcomp's native API works with a handle, the idea is to create a plan (data type, size, algorithm) and then this plan can be use over and over to compress or decompress data of the same size and type, on GPU (completely asynchronously, all the info needed to launch kernels is in the handle) or on CPU. Check the API in native/bitcomp.h. Here is an example of mixed compression and decompression on GPU and CPU using the native API.
Managed memory is used here to make the buffers visible on CPU and GPU, just to mix CPU and GPU for the example. Bitcomp can compress over PCIe (or nvlink) as well, for example with the uncompressed data in GPU memory, and the output buffer in host pinned memory. It works well if the compression is high enough for the PCIe bus to not be a bottleneck.
|
Hi gthomascollignon, thank you for your reply. Where i can find native bitcomp repository? I'm having some trouble finding it through google engine. |
I found https://github.com/boyuanzhang62/bitcomp_lossless_example/blob/master/bitcomp_example.cu |
This issue has been labeled |
This issue has been labeled |
Hi @andreamartini |
This issue has been labeled |
In the same way of deflate, zstandard, lz4 decompression, with which it is possible to decompress on cpu something compressed via GPU and nvcomp (i.e. using low level approach), i am interested in BITCOMP cpu decompression. That is, compress on GPU using nvcomp and BITCOMP, and then decompress on CPU (using BITCOMP or, maybe, other algorithm). If yes, is there some links where i can take a look?
Thank you.
The text was updated successfully, but these errors were encountered: