[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87v8bm5qqp.fsf@metaspace.dk>
Date: Wed, 04 Oct 2023 17:49:30 +0200
From: "Andreas Hindborg (Samsung)" <nmi@...aspace.dk>
To: Konstantin Shelekhin <k.shelekhin@...l.net>
Cc: Boqun Feng <boqun.feng@...il.com>,
Alice Ryhl <aliceryhl@...gle.com>, alex.gaynor@...il.com,
benno.lossin@...ton.me, bjorn3_gh@...tonmail.com, gary@...yguo.net,
jiangshanlai@...il.com, linux-kernel@...r.kernel.org,
ojeda@...nel.org, patches@...ts.linux.dev,
rust-for-linux@...r.kernel.org, tj@...nel.org, wedsonaf@...il.com,
yakoyoku@...il.com
Subject: Re: [PATCH v4 7/7] rust: workqueue: add examples
Hi,
"Konstantin Shelekhin" <k.shelekhin@...l.net> writes:
>> This is not a problem until nvmet actually uses/switches to Rust, right?
>> ;-) We can certainly improve the API when a real user needs something.
>> Or you know someone is already working on this?
>
> Nope, not at this moment. I have an itch to experiment with Rust and
> iSCSI, but that's my personal toy without any plans to at least propose
> it to the subsystem maintainers yet.
If you are so inclined, I would suggest you take a look at the blk-mq
bindings and the nvme (pci) [1] and null_blk [2] Rust drivers. I am
available if you have any questions!
BR Andreas
[1] https://github.com/metaspace/linux/tree/nvme-next-for-6.6
[2] https://github.com/metaspace/linux/tree/null_blk-next-for-6.6
Powered by blists - more mailing lists