From: Thomas Bertschinger <tahbertschinger@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: rust-for-linux@vger.kernel.org, linux-bcachefs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kbuild@vger.kernel.org,
kent.overstreet@linux.dev, bfoster@redhat.com, ojeda@kernel.org,
alex.gaynor@gmail.com, wedsonaf@gmail.com, masahiroy@kernel.org
Subject: Re: [PATCH RFC 0/3] bcachefs: add framework for internal Rust code
Date: Wed, 7 Feb 2024 18:14:15 -0700 [thread overview]
Message-ID: <20240208011415.GA574244@fedora-laptop> (raw)
In-Reply-To: <CANiq72=00+vZ+BqacSh+Xk8_VtNPVADH2Hcsyo-MPufojXvNFQ@mail.gmail.com>
On Wed, Feb 07, 2024 at 12:06:05PM +0100, Miguel Ojeda wrote:
> On Wed, Feb 7, 2024 at 6:57 AM Thomas Bertschinger
> <tahbertschinger@gmail.com> wrote:
> > I wasn't sure if this needed to be an RFC based on the current status
> > of accepting Rust code outside of the rust/ tree, so I designated it as
> > such to be safe. However, Kent plans to merge rust+bcachefs code in the
> > 6.9 merge window, so I hope at least the first 2 patches in this series,
> > the ones that actually enable Rust for bcachefs, can be accepted.
>
> This is worrying -- there has been no discussion about mixing C and
> Rust like this, but you say it is targeted for 6.9. I feel there is a
> disconnect somewhere. Perhaps it would be a good idea to have a quick
> meeting about this.
>
> Cheers,
> Miguel
That could be a good idea; what format do you suggest?
One question that I would like clarity on is if in general work to add
Rust into something like fs/bcachefs/ can be accepted at this point.
That is, is it realistic to expect that an upcoming kernel release could
include Rust code in fs/bcachefs/ at all (even if not in the form in
this patch series)?
Kent has been suggesting his plan to do this for a while, I think, but I
haven't yet seen many explicit statements about what would, and would
not be accepted into an upstream kernel for rust+bcachefs. (If I missed
any conversations where this was laid out, please let me know.)
Actually, the previous paragraphs in your email are helpful in terms
of laying out concrete expectations, so thank you.
You talk about using the broader kernel Rust APIs like the proposed VFS
layer. What about bindings for internal bcachefs APIs, like the btree
interface [1] that Kent mentioned in another response?
Would a v2 of this series, that removes the current 3rd patch and replaces
it with a patch to add in the bcachefs btree bindings, be more suitable
for acceptance upstream?
I think testing the VFS abstractions for bcachefs sounds like a very
worthwhile project--but it also sounds like a distinct project from
Kent's goals for integrating Rust into bcachefs in the near term.
[1] https://evilpiepirate.org/git/bcachefs-tools.git/tree/bch_bindgen/src/btree.rs
- Thomas Bertschinger
prev parent reply other threads:[~2024-02-08 1:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 5:55 [PATCH RFC 0/3] bcachefs: add framework for internal Rust code Thomas Bertschinger
2024-02-07 11:06 ` Miguel Ojeda
2024-02-07 20:57 ` Kent Overstreet
2024-02-07 21:33 ` Trevor Gross
2024-02-07 22:39 ` Darrick J. Wong
2024-02-08 4:19 ` Trevor Gross
2024-02-08 1:14 ` Thomas Bertschinger [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=20240208011415.GA574244@fedora-laptop \
--to=tahbertschinger@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=bfoster@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@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