Hello Bruce,
Thanks for sharing. However, IMHO using EAL for thread management in rust
is the wrong interface to expose.
EAL is a singleton object in DPDK architecture.
I see it as a hub for other resources.
Following that idea, the EAL structure can be divided to hold the
"original" resources inherited from librte_eal and new resources
introduced in Rust EAL.
Instead, I believe we should be
encouraging native rust thread management, and not exposing any DPDK
threading APIs except those necessary to have rust threads work with DPDK,
i.e. with an lcore ID. Many years ago when DPDK started, and in the C
world, having DPDK as a runtime environment made sense, but times have
changed and for Rust, there is a whole ecosystem out there already that we
need to "play nice with", so having Rust (not DPDK) do all thread
management is the way to go (again IMHO).
I'm not sure what exposed DPDK API you refer to.
Regards,
Gregory
