From: Hannes Reinecke <hare@suse.de>
To: "Andreas Hindborg (Samsung)" <nmi@metaspace.dk>,
lsf-pc@lists.linux-foundation.org
Cc: linux-block@vger.kernel.org, rust-for-linux@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>, Keith Busch <kbusch@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Damien Le Moal <dlemoal@kernel.org>,
Daniel Wagner <dwagner@suse.de>, Christoph Hellwig <hch@lst.de>,
Wedson Almeida Filho <wedsonaf@gmail.com>,
Boqun Feng <boqun.feng@gmail.com>,
Andreas Hindborg <a.hindborg@samsung.com>,
gost.dev@samsung.com
Subject: Re: [LSF/MM/BPF TOPIC] Rust block device driver APIs
Date: Mon, 29 Jan 2024 16:40:14 +0100 [thread overview]
Message-ID: <c7231bc2-37a1-43c6-b388-1005f299e584@suse.de> (raw)
In-Reply-To: <87v87cgsp8.fsf@metaspace.dk>
On 1/29/24 14:17, Andreas Hindborg (Samsung) wrote:
> Hi All,
>
> I would like to propose a session on the Rust block device driver APIs.
>
> I submitted the APIs along with a simple null block driver as an RFC last year
> [1]. Since then I have kept the code in sync with latest mainline release [2],
> cleaned up the code, and added a few features.
>
> After talking to some of you at various meetups over the past year, I think we
> have reached a point where we can potentially agree on merging initial Rust
> block layer support, along with the null block driver. To that end, I plan to
> send a few iterations of the patch set before LSF in May, so that we can use the
> session to discuss any remaining details.
>
> Since Kent has also proposed a dedicated Rust session, we might find some
> synergy with this topic [3].
>
> I also maintain an NVMe driver based on the Rust block APIs [4]. Due to
> community feedback, I have no plans for upstreaming this driver at the moment.
> However, it is a valuable tool for designing a sensible Rust block device API
> that is suitable real hardware.
>
> Part of the NVMe patches are abstractions for PCI. Other users (drm) have
> expressed interest in these, so I plan to separate these in their own tree to
> make them easier to pick up for those users.
>
> As a last note, I have recently become aware of ongoing work on
> implementing nbd in Rust. The work looks promising, and I hope the
> author will decide to send the patches, when they are ready to be
> shared.
>
And I had an intern converting nbd to rust, which I could present as a
proof-of-concept.
Or, rather, as a showcase how a (pretty basic) Rust driver would look
like. Idea is to have a side-by-side comparison and figure out if
a) writing driver in Rust would simplify the code
b) existing/requiring functionality can be matched
or, in short, if Rust lives up to its promises.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Ivo Totev, Andrew McDonald,
Werner Knoblich
prev parent reply other threads:[~2024-01-29 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 13:17 [LSF/MM/BPF TOPIC] Rust block device driver APIs Andreas Hindborg (Samsung)
2024-01-29 15:40 ` Hannes Reinecke [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=c7231bc2-37a1-43c6-b388-1005f299e584@suse.de \
--to=hare@suse.de \
--cc=a.hindborg@samsung.com \
--cc=axboe@kernel.dk \
--cc=boqun.feng@gmail.com \
--cc=dlemoal@kernel.org \
--cc=dwagner@suse.de \
--cc=gost.dev@samsung.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=nmi@metaspace.dk \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).