linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Andreas Hindborg <a.hindborg@kernel.org>,
	lsf-pc@lists.linux-foundation.org
Cc: linux-block@vger.kernel.org, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org, rust-for-linux@vger.kernel.org,
	Yiyang Wu <toolmanp@tlmp.cc>,
	toolmanp@outlook.com,
	linux-erofs mailing list <linux-erofs@lists.ozlabs.org>
Subject: Re: [LSF/MM/BPF TOPIC] Rust in FS, Storage, MM
Date: Mon, 17 Feb 2025 18:41:32 +0800	[thread overview]
Message-ID: <0290170c-39df-4609-8de1-55695d6ec0ad@linux.alibaba.com> (raw)
In-Reply-To: <87ldu9uiyo.fsf@kernel.org>



On 2025/2/14 14:41, Andreas Hindborg wrote:
> Hi All,
> 
> On behalf of the Linux kernel Rust subsystem team, I would like to suggest a
> general plenary session focused on Rust. Based on audience interest we would
> discuss:
> 
>   - Status of rust adoption in each subsystem - what did we achieve since last
>     LSF?
>   - Insights from the maintainers of subsystems that have merged Rust - how was
>     the experience?
>   - A reflection on process - does the current approach work or should we change
>     something?
>   - General Q&A

Last year Yiyang worked on an experimental Rust EROFS codebase and
ran into some policy issue (c+rust integration), although Rust
adaption is not the top priority stuff in our entire TODO list but
we'd like to see it could finally get into shape and landed as an
alternative part to replace some C code (maybe finally the whole
part) if anyone really would like to try to switch to the new one.

Hopefully some progress could be made this year (by Yiyang), but
unfortunately I have no more budget to travel this year, yet
that is basically the current status anyway.

Thanks,
Gao Xiang

> 
> Please note that unfortunately I will be the only representative from the Rust
> subsystem team on site this year.
> 
> Best regards,
> Andreas Hindborg
> 



      parent reply	other threads:[~2025-02-17 10:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14  6:41 Andreas Hindborg
2025-02-15  0:18 ` Steve French
2025-02-17 10:41 ` Gao Xiang [this message]

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=0290170c-39df-4609-8de1-55695d6ec0ad@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=a.hindborg@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=toolmanp@outlook.com \
    --cc=toolmanp@tlmp.cc \
    /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