weiji14 commented on issue #5090:
URL: https://github.com/apache/opendal/issues/5090#issuecomment-3054229212

   Awesome, glad that it worked 😄 
   
   > Although it keeps looking for `/etc/pki/tls/certs/ca-bundle.crt` even if 
you set `CURL_CA_BUNDLE`
   
   Maybe related to this issue - https://github.com/rapidsai/kvikio/issues/711? 
It seems like @TomAugspurger had a fix for this in 
https://github.com/TomAugspurger/kvikio/commit/73842e26afa259c3b9bc79dd8a0204735d014985.
   
   > However, after some research, I found that even if we create a Rust 
binding for KvikIO, it might not be sufficient.
   > 
   > The reason is that to utilize GDS, we need to use the CUDA API to manage 
GPU memory. Unfortunately, there is not yet a mature Rust library for CUDA.
   
   Just to somewhat go back to the core topic of "how to create Rust bindings 
to GDS", I'm wondering if we want to wrap just the low-level `cuFile` (which 
cudarc is getting to at https://github.com/coreylowman/cudarc/issues/403), or 
the higher-level `kvikIO` (which wraps `cuFile`, but also has a non-CUDA 
compatibility mode for CPU fallback). I've been reading 
https://github.com/rapidsai/kvikio/issues/686#issuecomment-2810921936, and my 
impression is that kvikIO's cuFile (Python & C++?) bindings will eventually be 
moved out of kvikIO, though not sure how that would happen, but maybe best to 
exercise caution on which part of kvikIO's API to wrap in Rust until then.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to