Linux 6.18 To Allow Rust And C Code To Use The Same Memory Model
The latest tranche of Rust code ready to go for the upcoming Linux 6.18 kernel is now ready to go and has been queued into a TIP branch ahead of the merge window.
The latest work on Rust atomic changes for the Linux kernel have been queued into tip/tip.git's "locking/core" branch and now putting it on trajectory for landing in the Linux 6.18 merge window in two weeks.
The Rust atomic changes for this next kernel version include support for the generic Linux Kernel Memory Model (LKMM) atomic variables within Rust. The patch series explains that this ensures the Rust and C sides are using the same memory model when communicating with each other. In turn it also unblocks a few more fine-grained concurrent code in Rust.
The patch series also adds a wrapper to the kernel's "refcount_t" in Rust to avoid needing customized reference counting code in Rust.
The patches for now are in the locking/core branch and barring any objections from Linus Torvalds should in turn appear in Linux 6.18.
The latest work on Rust atomic changes for the Linux kernel have been queued into tip/tip.git's "locking/core" branch and now putting it on trajectory for landing in the Linux 6.18 merge window in two weeks.
The Rust atomic changes for this next kernel version include support for the generic Linux Kernel Memory Model (LKMM) atomic variables within Rust. The patch series explains that this ensures the Rust and C sides are using the same memory model when communicating with each other. In turn it also unblocks a few more fine-grained concurrent code in Rust.
The patch series also adds a wrapper to the kernel's "refcount_t" in Rust to avoid needing customized reference counting code in Rust.
👁 Rust atomic patches for Linux 6.18
The patches for now are in the locking/core branch and barring any objections from Linus Torvalds should in turn appear in Linux 6.18.