async-rdma
async-rdma copied to clipboard
datenlord
Easy to use RDMA API in Rust async
Hello, I was using PyO3 to bind this rust code to python and is now struggling with the memory ownership problem (more specifically, double free). When I try to pass...
A stream with guaranteed ordering based on send and receive. - send next packet after previous packet have been submitted in queuepair， another thread will wait for ack and handle...
I tried to run the example as show in repo index page like: ```bash cargo run --example rpc ``` ```bash cargo run --example rpc Finished dev [unoptimized + debuginfo] target(s)...
When I tried to run client and server of example, I got a message as follow: thread 'tokio-runtime-worker' panicked at 'internal error: entered unreachable code: dalloc failed, check if JEMALLOC_RETAIN...
For #111 , the better solution is to bump rust toolchain to a higher version. And it needs some change to satisfy clippy's checks.
The API to create MR, i.e. alloc_local_mr(layout) function, only has the option to allocate new memory in an ad-hoc way (use malloc inside the alloc_local_mr function). Is it possible that...
It seems like something happened to one of the deps, possibly recently? > cargo build --example rpc > Updating crates.io index >error: failed to select a version for the requirement...
This goes with the issue I posted. The examples compile and run now...
The value of immediate data flag may be different on RDMA devices. And you can change this flag by [this API](https://github.com/datenlord/async-rdma/blob/39e26c6cf0317229a0b7dbc557b0f6fe2824ec7b/src/lib.rs#L1009) to adapt your devices. _Originally posted by @GTwhy in...
Like such: https://github.com/datenlord/async-rdma/blob/d445d692cc2aea9e27dc86c4d1311f9b5b85e586/src/queue_pair.rs#L209 https://github.com/datenlord/async-rdma/blob/d445d692cc2aea9e27dc86c4d1311f9b5b85e586/src/queue_pair.rs#L807 And what does the 'SAFETY: POD FFI type' mean?
