qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hanna Czenczek <hreitz@redhat.com>
To: Qemu-block <qemu-block@nongnu.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Release of RSD (Rust QSD) 0.1
Date: Wed, 7 Jun 2023 17:01:17 +0200	[thread overview]
Message-ID: <24269db5-2464-0eb6-2f39-ed8a6d1aca58@redhat.com> (raw)

Hi everyone!

I’ve just released the first version (0.1) of RSD, which is a 
proof-of-concept to rewrite the qemu-storage-daemon (QSD) and thus the 
qemu block layer in Rust:

https://gitlab.com/hreitz/rsd
https://gitlab.com/hreitz/rsd/-/releases/v0.1

We’ve been talking for quite a long time about adding Rust into qemu and 
the qemu block layer, and usually ended it with “Could be nice, we just 
need someone to start.”  After we’ve had discussion last year about 
maybe adding C++ for language-supported coroutines, I thought if the 
time isn’t now, it’s never.

In the process, I’ve gathered some insights into obstacles and benefits 
that Rust could bring us, which I’ve summed up in two blog posts:

Part 1 (Overview): https://czenczek.de/blog/rsd-overview.html
Part 2 (Performance): https://czenczek.de/blog/rsd-performance.html

The bottom line so far is that Rust could bring us valuable benefits, 
but likely only if we rewrote everything.  A middle ground is possible, 
by keeping RSD focused on a specific subset of functionality, the one 
that is most valuable for it.  In any case, this (v0.1) is as far as is 
reasonable to go with RSD as an experiment – any further work we’d need 
to do in earnest and define what exactly we actually want.  And that’s 
an important part of what this announcement is for, to see whether 
anyone has this interest!


Hanna



                 reply	other threads:[~2023-06-07 15:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=24269db5-2464-0eb6-2f39-ed8a6d1aca58@redhat.com \
    --to=hreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.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).