From: Andreas Hindborg <a.hindborg@kernel.org>
To: Matthew Wilcox <willy@infradead.org>, Daniel Gomez <da.gomez@kernel.org>
Cc: linux-mm@kvack.org, lsf-pc@lists.linux-foundation.org,
Alice Ryhl <aliceryhl@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Daniel Gomez <da.gomez@samsung.com>,
gost.dev@samsung.com, Greg KH <gregkh@linuxfoundation.org>,
Julia Lawall <julia.lawall@inria.fr>,
Kairui Song <kasong@tencent.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>,
rust-for-linux@vger.kernel.org,
Tamir Duberstein <tamird@gmail.com>
Subject: Re: [LSF/MM/BPF TOPIC] Evaluating Rust for XArray
Date: Tue, 17 Feb 2026 18:51:28 +0100 [thread overview]
Message-ID: <87bjhncl7j.fsf@kernel.org> (raw)
In-Reply-To: <aZR-ItMBkiqyBdKd@casper.infradead.org>
"Matthew Wilcox" <willy@infradead.org> writes:
> On Tue, Feb 17, 2026 at 03:28:45PM +0100, Daniel Gomez wrote:
>> We propose a topic to discuss the potential use of Rust in core Linux
>> kernel data structures.
>
> This is premature? We can't move the pagecache or swap over to use Rust
> until we can compile Rust for m68k/parisc/alpha/... or we drop those
> architectures from the tree.
I disagree that this is premature. And I don't think Daniel is
suggesting we swap anything over at this time. Doing this work is not
the same as swapping anything over.
We don't have to wait 5-10 years for gcc to fully support Rust, before
we start playing with this. We can, and should, start evaluating if we
can deploy Rust in this area now. We might find that we are lacking
something from the Rust language to do what we want. We can work with
the Rust developers to make sure that the Rust language gets all the
bells and whistles that it needs, to support the use cases we have for
the Linux kernel. I think this would benefit everyone. Let's get in
early and help shape the language, rather than board in 10 years when
everything is settled and much more difficult to change.
On the other hand, we might also find that no, Rust does not work for
this. This would be a valuable outcome as well.
At any rate, this is not a call to end support for all architectures
that do not support Rust. Rather, this is a call to figure out if we
should work harder on getting Rust support for m68k et al.
Without doing this exploration, we cannot answer the questions.
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2026-02-17 17:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 14:28 Daniel Gomez
2026-02-17 14:41 ` Matthew Wilcox
2026-02-17 17:51 ` Andreas Hindborg [this message]
2026-02-17 20:14 ` Miguel Ojeda
2026-02-18 8:47 ` Andreas Hindborg
2026-02-17 20:18 ` Miguel Ojeda
2026-02-18 11:24 ` Daniel Gomez
2026-02-17 14:44 ` Tamir Duberstein
2026-02-17 18:57 ` Andreas Hindborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bjhncl7j.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=da.gomez@kernel.org \
--cc=da.gomez@samsung.com \
--cc=gost.dev@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--cc=kasong@tencent.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox