From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Hayley Leblanc <hleblanc@utexas.edu>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
rust-for-linux <rust-for-linux@vger.kernel.org>,
Vijay Chidambaram <vijayc@utexas.edu>,
Samantha Miller <samantha.a.miller123@gmail.com>,
austin.chase.m@gmail.com
Subject: Re: Persistent memory file system development in Rust
Date: Thu, 27 Jan 2022 15:09:53 +0100 [thread overview]
Message-ID: <CANiq72=fTTreGHn_-t1tBLKxMeCr4b0ENsHGAgWZL1OZ7sKhMA@mail.gmail.com> (raw)
In-Reply-To: <YfHU5/RrpJlRx5sO@casper.infradead.org>
On Thu, Jan 27, 2022 at 3:59 AM Matthew Wilcox <willy@infradead.org> wrote:
>
> ... This time with the correct email address for the Rust list.
Thanks for the Cc, Willy!
> On Wed, Jan 26, 2022 at 10:35:19PM +0000, Matthew Wilcox wrote:
> > On Tue, Jan 25, 2022 at 04:02:56PM -0600, Hayley Leblanc wrote:
> >
> > I only have a toe in Rust development, but I'm not aware of
> > any work being done specifically for filesystems, that said ...
For your reference: a RamFS port was posted last week. It uses the
Rust for Linux support plus `cbindgen` to take an incremental
approach, see:
https://lore.kernel.org/rust-for-linux/35d69719-2b02-62f2-7e2f-afa367ee684a@gmail.com/
> > Bento seems like a good approach (based on a 30 second scan of their
> > git repo). It wasn't on my radar before, so thanks for bringing it up.
> > I think basing your work on Bento is a defensible choice; it might be
> > wrong, but the only way to find out is to try.
Side note: Bento is not using the Rust for Linux support (as far as I
know / yet).
Cheers,
Miguel
next prev parent reply other threads:[~2022-01-27 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFadYX5iw4pCJ2L4s5rtvJCs8mL+tqk=5+tLVjSLOWdDeo7+MQ@mail.gmail.com>
[not found] ` <YfHMp+zhEjrMHizL@casper.infradead.org>
2022-01-26 23:10 ` Persistent memory file system development in Rust Matthew Wilcox
2022-01-27 14:09 ` Miguel Ojeda [this message]
2022-01-27 16:48 ` Hayley Leblanc
2022-01-27 20:07 ` Theodore Y. Ts'o
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='CANiq72=fTTreGHn_-t1tBLKxMeCr4b0ENsHGAgWZL1OZ7sKhMA@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=austin.chase.m@gmail.com \
--cc=hleblanc@utexas.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=samantha.a.miller123@gmail.com \
--cc=vijayc@utexas.edu \
--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;
as well as URLs for NNTP newsgroup(s).