News for hackers. Stuff that matters.

A comment on Zero-cost futures in Rust. Parent comment

Re:Zero-cost futures in Rust by lightcatcher on Thursday August 11, 2016 @05:31PM (#12271701)
> Why would you write networking code in C in 2016, when there are better alternatives available (like this one)?

Support for kernel bypass networking libraries like ibverbs, DPDK (has an old unmaintained Rust wrapper) and other IO kernel bypass libraries such as SPDK and IOAT.

If Rust supported these libraries, I'd much prefer the future based Rust code to a massive event loop in C.

[ Parent | on HN ]
Re:Zero-cost futures in Rust by benlwalker on Friday August 12, 2016 @03:05AM (#12273807)
I'm one of the authors of SPDK (which includes an NVMe driver and an IOAT driver). If the community wants to add rust bindings to those two components I'd be very supportive.
[ Parent | on HN ]
Re:Zero-cost futures in Rust by JoshTriplett on Thursday August 11, 2016 @05:46PM (#12271812)
The article mentioned that the authors would love to help make futures-based wrappers for C libraries. You might ask if they could help with wrappers for ibverbs, DPDK, SPDK, and IOAT.
[ Parent | on HN ]
Re:Zero-cost futures in Rust by bluejekyll on Thursday August 11, 2016 @06:21PM (#12272058)
It's all open-source, this is an area that if it matters this much to you, you could help support. The Rust community is hugely welcoming to people coming on and helping.
[ Parent | on HN ]