From: Matthew Sakai <msakai@redhat.com>
To: dm-devel@lists.linux.dev
Cc: Matthew Sakai <msakai@redhat.com>
Subject: [PATCH 0/3] dm vdo: improve documentation
Date: Thu, 8 Feb 2024 13:09:12 -0500 [thread overview]
Message-ID: <cover.1707415327.git.msakai@redhat.com> (raw)
Add details about I/O handling in vdo, and details about
concurrency and locking. Also add vdo documentation to
the device-mapper doc index.
Matthew Sakai (3):
dm vdo: add vdo documentation to device-mapper index
dm vdo: add vio lifecycle details to doc
dm vdo: add documentation details on zones and locking
.../admin-guide/device-mapper/index.rst | 2 +
.../admin-guide/device-mapper/vdo-design.rst | 674 ++++++++++++------
drivers/md/dm-vdo/block-map.h | 15 +
drivers/md/dm-vdo/dedupe.c | 5 +
drivers/md/dm-vdo/recovery-journal.h | 4 +
drivers/md/dm-vdo/slab-depot.h | 16 +-
6 files changed, 483 insertions(+), 233 deletions(-)
--
2.42.0
next reply other threads:[~2024-02-08 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 18:09 Matthew Sakai [this message]
2024-02-08 18:09 ` [PATCH 1/3] dm vdo: add vdo documentation to device-mapper index Matthew Sakai
2024-02-08 18:09 ` [PATCH 2/3] dm vdo: add vio lifecycle details to doc Matthew Sakai
2024-02-08 18:09 ` [PATCH 3/3] dm vdo: add documentation details on zones and locking Matthew Sakai
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=cover.1707415327.git.msakai@redhat.com \
--to=msakai@redhat.com \
--cc=dm-devel@lists.linux.dev \
/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.