All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <heinzm@redhat.com>
To: heinzm@redhat.com, dm-devel@redhat.com
Cc: scott.bauer@intel.com
Subject: [PATCH v4 0/2] dm unstriped: add new target
Date: Mon, 18 Dec 2017 19:08:50 +0100	[thread overview]
Message-ID: <cover.1513618685.git.heinzm@redhat.com> (raw)

This is a quick rework of the new "unstripe" target
(undoes a striped/raid0 mapping) v3 patch series
authored by Scott Bauer addressing some points
discussed here and more.

Addressed:
- rename target to "unstriped"
- enhance constructor header
- add more consistency checks to constructor imposing
  divisibility of device and drive length by chunk size;
  device length has to be divisible by total number of drives
- use destructor in constructor error pathes
- move a few local variables to 'struct unstripe'
- add missing unstripe_status() function using
  new variables in ^ struct to address requirement
  for dm targets
- tweaked config variable name Kconfig text

Not addressed:
- documentation (kept as is in this series for completeness) 

Example of 'dmsetup table' output:
# dmsetup table nvm-s s1 s2
nvm-s: 0 262144 raid raid0 1 8 2 - 254:2 - 254:3
s1: 0 131072 unstriped 254:4 0 2 8
s2: 0 131072 unstriped 254:4 1 2 8


Scott,
please check, test and tell, if the additonal constraints
on length divisibility are too restrictive and how to go
about the 2 FIXMEs.


Tested-by: Heinz Mauelshagen <heinzm@redhat.com>

Heinz Mauelshagen (2):
  dm unstriped: new "unstriped" raid0/striped device
  dm unstriped: add documentation for unstriped target

 Documentation/device-mapper/dm-unstripe.txt | 130 ++++++++++++++++
 drivers/md/Kconfig                          |  11 ++
 drivers/md/Makefile                         |   1 +
 drivers/md/dm-unstripe.c                    | 233 ++++++++++++++++++++++++++++
 4 files changed, 375 insertions(+)
 create mode 100644 Documentation/device-mapper/dm-unstripe.txt
 create mode 100644 drivers/md/dm-unstripe.c

-- 
2.14.3

             reply	other threads:[~2017-12-18 18:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 18:08 Heinz Mauelshagen [this message]
2017-12-18 18:08 ` [PATCH v4 1/2] dm unstriped: the target Heinz Mauelshagen
2017-12-18 18:08 ` [PATCH v4 2/2] dm unstriped: add documentation for target Heinz Mauelshagen
2017-12-18 23:22 ` [PATCH v5] dm: add unstriped target Mike Snitzer
2017-12-18 23:15   ` Scott Bauer
2017-12-19 17:25   ` Scott Bauer
2017-12-19 18:13   ` Scott Bauer
2017-12-19 18:35   ` Scott Bauer
2017-12-19 20:03     ` Mike Snitzer
2017-12-19 20:16       ` Scott Bauer
2017-12-19 21:38         ` Mike Snitzer

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.1513618685.git.heinzm@redhat.com \
    --to=heinzm@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=scott.bauer@intel.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.