From: "Qingsong Chen" <changxian.cqs@antgroup.com>
To: linux-kernel@vger.kernel.org
Cc: 田洪亮 <tate.thl@antgroup.com>,
"Qingsong Chen" <changxian.cqs@antgroup.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
rust-for-linux@vger.kernel.org
Subject: [RFC PATCH 0/8] Rust device mapper abstractions
Date: Sun, 25 Jun 2023 20:16:49 +0800 [thread overview]
Message-ID: <20230625121657.3631109-1-changxian.cqs@antgroup.com> (raw)
Hello!
This is a version of device mapper abstractions. Based on
these, we also implement a linear target as a PoC.
Any suggestions are welcomed, thanks!
Additionally, there are some dummy codes used to wrap the block
layer structs, i.e., `bio` and `request`, which seems being
in the review process, so I just place it in the same file.
Qingsong Chen (8):
rust: kernel: add basic abstractions for device-mapper
rust: kernel: add request related TargetOperations
rust: kernel: add some hook TargetOperations
rust: kernel: add some info handler TargetOperations
rust: kernel: add underlying device related TargetOperations
rust: kernel: add DAX related TargetOperations
rust: kernel: prepare to implement dm target in Rust
samples: rust: add a device mapper linear target
rust/bindings/bindings_helper.h | 2 +
rust/helpers.c | 7 +
rust/kernel/device_mapper.rs | 1279 +++++++++++++++++++++++++++++++
rust/kernel/lib.rs | 1 +
samples/rust/Kconfig | 10 +
samples/rust/Makefile | 1 +
samples/rust/rust_dm_linear.rs | 257 +++++++
7 files changed, 1557 insertions(+)
create mode 100644 rust/kernel/device_mapper.rs
create mode 100644 samples/rust/rust_dm_linear.rs
--
2.40.1
next reply other threads:[~2023-06-25 12:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 12:16 Qingsong Chen [this message]
2023-06-25 12:16 ` [RFC PATCH 1/8] rust: kernel: add basic abstractions for device-mapper Qingsong Chen
2023-06-25 12:25 ` Greg KH
2023-06-26 3:26 ` Qingsong Chen
2023-06-26 16:39 ` Boqun Feng
2023-07-14 15:48 ` Benno Lossin
2023-07-17 3:04 ` Qingsong Chen
2023-06-25 12:16 ` [RFC PATCH 2/8] rust: kernel: add `request` related TargetOperations Qingsong Chen
2023-07-14 15:49 ` Benno Lossin
2023-07-17 3:42 ` Qingsong Chen
2023-06-25 12:16 ` [RFC PATCH 3/8] rust: kernel: add some hook TargetOperations Qingsong Chen
2023-06-25 12:16 ` [RFC PATCH 4/8] rust: kernel: add some info handler TargetOperations Qingsong Chen
2023-06-25 12:16 ` [RFC PATCH 5/8] rust: kernel: add underlying device related TargetOperations Qingsong Chen
2023-06-25 12:16 ` [RFC PATCH 6/8] rust: kernel: add DAX " Qingsong Chen
2023-06-25 12:16 ` [RFC PATCH 7/8] rust: kernel: prepare to implement dm target in Rust Qingsong Chen
2023-06-25 12:16 ` [RFC PATCH 8/8] samples: rust: add a device mapper linear target Qingsong Chen
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=20230625121657.3631109-1-changxian.cqs@antgroup.com \
--to=changxian.cqs@antgroup.com \
--cc=alex.gaynor@gmail.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tate.thl@antgroup.com \
--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;
as well as URLs for NNTP newsgroup(s).