linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Daniel Gomez <da.gomez@kernel.org>
Cc: linux-mm@kvack.org, lsf-pc@lists.linux-foundation.org,
	Alice Ryhl <aliceryhl@google.com>,
	Andreas Hindborg <a.hindborg@kernel.org>,
	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 14:41:38 +0000	[thread overview]
Message-ID: <aZR-ItMBkiqyBdKd@casper.infradead.org> (raw)
In-Reply-To: <aZRncP-sKLLS2K1U@macos>

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.



  reply	other threads:[~2026-02-17 14:41 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 [this message]
2026-02-17 17:51   ` Andreas Hindborg
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=aZR-ItMBkiqyBdKd@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=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 \
    /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