4 ms·
> Funny you ask, I was wondering the same thing last night so I went through the rust-for-linux mailing list archive. This thread is pretty telling: > https://
by Aurornis 3y ago
> Funny you ask, I was wondering the same thing last night so I went through the rust-for-linux mailing list archive. This thread is pretty telling:
> https://lore.kernel.org/rust-for-linux/bddea099-4468-4f96-2e06-2b207b608485@usi.ch/ https://lore.kernel.org/rust-for-linux/bddea099-4468-4f96-2e...
> https://lore.kernel.org/rust-for-linux/c61a60ef-fa9d-44ea-9852-ae7b18bc1ab1@lunn.ch/ https://lore.kernel.org/rust-for-linux/c61a60ef-fa9d-44ea-98...
I don’t see how either post supports your points. The first is about OOT vs in-tree modules and the second isn’t about anything specific to Rust. You just picked a random post from someone learning about kernel development who happened to be using Rust.
The people doing core Rust for Linux work (not random mailing list participants) are actually very qualified and very knowledgeable about Linux. I don’t think your characterization of them is fair at all.
Grabbing random mailing list posts from non core maintainers and trying to extrapolate conclusions about an entire multi-year is not a good way to evaluate a project.
- patrick451 3y agoI don't have a dog in this fight, but " someone learning about kernel development who happened to be using Rust" sounds to me like anecdotal evidence for the assertion that most rust contributors don't know how kernel development works.
- i_am_a_peasant 3y agomy point exactly..
- i_am_a_peasant 3y ago>The people doing core Rust for Linux work (not random mailing list >participants) are actually very qualified and very knowledgeable about > Linux. I don’t think your characterization of them is fair at all. Alright, they are very qualified and knowledgeable, what is a fair characterization of the work they're doing? It's been a year, let's see how much stuff they managed to merge, My terminal window has 135 rows: cd linux/ git log --oneline rust/ output <space> output <space> output <space> no output Oh wow, how many people was it again? git shortlog -s -n -e --all --no-merges rust/ | wc -l 29 Most of those guys have single digits number of commits and there are 7 guys with double digits number of commits so let's say there's about 7 people most active doing rust in linux. Do you know Rust yourself? Take a look at the bulk of the patches that got merged, could you write that if someone paid you? My guess is yes, because it looks pretty average to me. (No offense to you personally).
- nevi-me 3y agoThere's been 1500+ commits since 2020 on the 'main' Kernel fork that has Rust support [0]. Many of them through collaboration and backs and forths of review (look at the PRs on the fork). My understanding is that the `rust-next` branch represents what's ready for Linus to merge. So there's a whole lot that's not in there, which you're missing in your evaluation. Last year a Kernel dev from Western Digital wrote an NVME driver in Rust [1] (look at slides 15 & 16) which I would consider to be qualified and knowledgeable. I wouldn't measure the effort solely on what's been merged to mainline as there's been 6 merge windows from 6.1 to now. Many of those commits are laying the groundwork for the next few years. [0] https://github.com/torvalds/linux/compare/master...Rust-for-Linux:linux:rust https://github.com/torvalds/linux/compare/master...Rust-for-... [1] https://lpc.events/event/16/contributions/1180/attachments/1017/1961/deck.pdf https://lpc.events/event/16/contributions/1180/attachments/1...
- i_am_a_peasant 3y ago> Last year a Kernel dev from Western Digital wrote an NVME driver in Rust [1] (look at slides 15 & 16) which I would consider to be qualified and knowledgeable. NVMe drives are probably the simplest form of storage you can possibly think of in today's day and age, from a user perspective. Which is a perfect candidate for a proof of concept like that. Not saying that it's not good work. In those 1500+ commits I see a lot of noise, and some good stuff, I like the alloc stuff, chardevs, buffer management, the async executor stuff looks really good scrolls scrolls, scrolls, okay yes. A lot of this stuff looks meaningful and I hope to see it merged in the near future.