From: "Bryn M. Reeves" <breeves@redhat.com>
To: "Pra.. Dew.." <linux_learner@outlook.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>,
Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [dm-devel] setting up dmverity using device mapper IOCTLs
Date: Mon, 12 Sep 2022 16:59:39 +0100 [thread overview]
Message-ID: <Yx9Xa47V9REfs2+c@redhat.com> (raw)
In-Reply-To: <BY5PR14MB389395BF1BEB0118582907A186449@BY5PR14MB3893.namprd14.prod.outlook.com>
On Mon, Sep 12, 2022 at 03:37:19PM +0000, Pra.. Dew.. wrote:
> Thank you Zdenek. We are developing a embedded system with very constrained memory/storage. So we are trying to see if we can combine utilities like dmsetup with other Rust code for managing storage in our embedded system, while only including the parts of dmsetup that we really need. Hence I am trying to figure out what is the best way here.
If you are working with Rust then you may want to evaluate the
devicemapper-rs library:
https://github.com/stratis-storage/devicemapper-rs/
This is an implementation of a high level interface to the DM ioctls in
Rust - it obtains some constants from libdevmapper.h via bindgen but the
ioctl handling and header parsing is done natively.
It's been around for a while and is used by Stratis and some other
projects. There have been a few discussions around a new userspace DM
implementation in Rust with a somewhat different interface but nothing
has been written so far.
Regards,
Bryn.
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2022-09-12 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 18:46 [dm-devel] setting up dmverity using device mapper IOCTLs Pra.. Dew..
2022-09-12 5:55 ` [dm-devel] Location for the definition of dm_task Pra.. Dew..
2022-09-12 12:54 ` Zdenek Kabelac
2022-09-12 13:01 ` [dm-devel] setting up dmverity using device mapper IOCTLs Zdenek Kabelac
2022-09-12 15:37 ` Pra.. Dew..
2022-09-12 15:59 ` Bryn M. Reeves [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=Yx9Xa47V9REfs2+c@redhat.com \
--to=breeves@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux_learner@outlook.com \
--cc=zkabelac@redhat.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 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.