NPP has many functions that perform a binary operation in which one of the operands is a constant. However, these functions assume the constant is in host memory. I regularly find cases in which I want to perform an operation against a constant where the constant is in device memory. I use existing NPP functions to calculate that constant, but then would need to transfer the constant to host memory in order to perform the next NPP function call I need. This doesn’t work so well when I’m using async calls. Any way functions with constants in device memory could be added to NPP? I’d be surprised if they weren’t almost exact copies of the existing functions that perform binary ops with one constant operand.
The suggested way to request changes/additions/improvements to CUDA is to file a bug.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Calling NPP functions with GPU pointers | 1 | 4883 | December 8, 2009 | |
Use of Npp lib with CUDA? | 2 | 1430 | June 18, 2010 | |
npp and parallelism | 2 | 609 | October 18, 2021 | |
Cuda constant memory | 5 | 2213 | September 7, 2023 | |
Does the CUDA function throw an exception? | 3 | 2103 | July 29, 2018 | |
Passing a pointer to __constant__ memory as a parameter for a __device__ function | 2 | 1487 | March 29, 2022 | |
CUDA parallel execution of NPP functions | 0 | 1438 | November 8, 2012 | |
can NPP functions work async ? | 1 | 1571 | February 9, 2010 | |
npp library function argument *pDeviceBuffer | 5 | 965 | June 14, 2011 | |
NPP expansion Limitations in the NPP methods | 2 | 10695 | August 2, 2010 |