3 ms·
Looks interesting and definitely promising Though it would probably make sense to make the API more "Rust like" and avoid things like the multiple cstr!() Som
by raverbashing 7y ago
Looks interesting and definitely promising
Though it would probably make sense to make the API more "Rust like" and avoid things like the multiple cstr!()
Some things are definitely trickier than others, for example how to deal with the different options of kmalloc if it's rust that's allocating memory
- geofft 7y agoFeedback is definitely welcome! Re cstr see https://github.com/fishinabarrel/linux-kernel-module-rust/issues/16 https://github.com/fishinabarrel/linux-kernel-module-rust/is... and https://github.com/fishinabarrel/linux-kernel-module-rust/pull/133 https://github.com/fishinabarrel/linux-kernel-module-rust/pu... . What we have now is definitely better than b"foo\0" but not the best possible thing. I think there's work upstream on custom / multiple allocators; we'll plug the various kmalloc(GFP_FOO) flags into that once it exists. It is super beneficial to use the standard library's collections and third-party crates that use them.