On Thu, Apr 22, 2021 at 11:29 PM Miguel Ojeda <miguel.ojeda.sandonis@xxxxxxxxx> wrote: > > But as subsystem maintainer I'd like a clear picture of this wrapper > > overhead, what does it usually entail? A typical kernel API has > > vtable and a few variables, not much more than that. > > If you mean runtime-overhead, i.e. performance, it should be very > small or even zero. It should be possible to perform LTO across > languages too. > > If you mean source code overhead, or cognitive overhead, then it is > quite a bit, yes. Please see below. Yeah that is what I mean :) > I hear you! I do not think it will take decades for kernel developers > to get up to speed, but I agree that having some help/backup is a very > good idea in the beginning. > > Our hope is that, if Rust advantages prove themselves, then it will > the subsystem maintainers the ones that will want to create and > maintain the wrappers so that drivers in their tree are easier to > maintain and less prone to mistakes ;-) I am not really convinced that (leaf) drivers is where Rust will help most. As I mentioned in my mail to Wedson that I think things like network protocols that deal with abstract entities will have more "pure code" (not deal with machine registers, just RAM memory). File systems would be another example. I think the Rust proponents should be open to the fact that their work will eventually depend on themselves or someone else fixing a working compiler for the maintained architectures in the Linux kernel one way or the other, so they will be able to work with Rust project anywhere in the kernel. For example m68k is not going away. Avoiding this question of compiler support, just waiting and hoping that these old architectures will disappear is the wrong idea. The right idea is to recognize that LLVM and/or GCC Rust needs to support all these architectures so they can all use Rust. Someone needs to put in the effort. After all fixing that compiler support is an insignificant amount of work compared to what Rust in the core kernel will be. Yours, Linus Walleij
