From: Andreas Hindborg <a.hindborg@kernel.org>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-block@vger.kernel.org, "Jens Axboe" <axboe@kernel.dk>,
"Matthew Wilcox" <willy@infradead.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>
Subject: [LSF/MM/BPF TOPIC] Rust block layer abstractions and benchmark strategies
Date: Tue, 21 Jan 2025 12:13:48 +0100 [thread overview]
Message-ID: <871pwwctcj.fsf@kernel.org> (raw)
I All,
I would like to propose that we have a session on Rust in the block
layer again this year. Specifically I would like to discuss some rather
puzzling results I observe when I benchmark the C and Rust null block
drivers. I did a write up of the challenges I face at [1]. The
observations are not tied to rust, they also manifest in the C driver.
Being able to consistently benchmark performance of the null block
driver is rather important in terms of validating Rust for use in the
block layer. I would hope to be able to collect some feedback on these
issues during a session.
If time permits, I would like to give a status update on the efforts of
building a feature complete null block driver in Rust. I will send
additional patches that enable memory backed devices and timer
completions before the Summit. Most of the patches have been ready for a
while, but they are pending merge of dependencies (xarray, hrtimer,
module_params).
If anyone is interested, I would make myself available for deep dives on
the Rust block layer code base, 1:1 or tutorial style. We (the Rust
kernel hackers) have had some good experiences with these kinds of
sessions in other subsystems.
Best regards,
Andreas Hindborg
[1] https://metaspace.github.io/2024/12/02/problems-in-benchmark-land.html
next reply other threads:[~2025-01-21 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 11:13 Andreas Hindborg [this message]
2025-01-21 12:04 ` [Lsf-pc] [LSF/MM/BPF TOPIC] Rust block layer abstractions and benchmark strategies Jan Kara
2025-01-21 12:51 ` Andreas Hindborg
2025-01-21 13:18 ` Jan Kara
2025-01-22 9:52 ` Niklas Cassel
2025-01-23 8:56 ` Andreas Hindborg
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=871pwwctcj.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.org \
--cc=ojeda@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.