From: Mike Snitzer <snitzer@redhat.com>
To: Scott Bauer <scott.bauer@intel.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
dm-devel@redhat.com, agk@redhat.com,
linux-kernel@vger.kernel.org, keith.busch@intel.com,
jonathan.derrick@intel.com
Subject: Re: [PATCH v4 1/2] dm-unstripe: unstripe RAID 0/dm-striped device
Date: Mon, 18 Dec 2017 14:32:49 -0500 [thread overview]
Message-ID: <20171218193249.GA6149@redhat.com> (raw)
In-Reply-To: <20171218185235.fcxbqb77fv733h5v@sbauer-Z170X-UD5>
On Mon, Dec 18 2017 at 1:52pm -0500,
Scott Bauer <scott.bauer@intel.com> wrote:
>
> > > +config DM_UN_STRIPE
> > > + tristate "Transpose IO to individual drives on a raid device"
> > > + depends on BLK_DEV_DM
> > > + ---help---
> > > + Enable this feature if you with to unstripe I/O on a RAID 0
> > > + device to the respective drive. If your hardware has physical
> > > + RAID 0 this module can unstripe the I/O to respective sides.
> >
> > What does "sides" mean above?
>
> Should say, "members". There's also an alternative patch set out by Heinz
> that I am currently testing/writing comments for. It looks like we'll use
> his version after I submit my comments (IE take the stuff I put in my v4
> to fix your comments).
Can you be more specific? I've not seen anything from Heinz.
I've been reviewing your v4 and modified it to match dm-stripe.c more
(like Alasdair asked for).
Mike
next prev parent reply other threads:[~2017-12-18 19:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 17:28 [PATCH v4 0/2] dm-unstripe Scott Bauer
2017-12-18 17:28 ` [PATCH v4 1/2] dm-unstripe: unstripe RAID 0/dm-striped device Scott Bauer
2017-12-18 19:11 ` Randy Dunlap
2017-12-18 18:52 ` Scott Bauer
2017-12-18 19:32 ` Mike Snitzer [this message]
2017-12-18 19:37 ` Mike Snitzer
2017-12-20 10:01 ` kbuild test robot
2017-12-20 10:01 ` kbuild test robot
2017-12-20 10:21 ` kbuild test robot
2017-12-20 10:21 ` kbuild test robot
2017-12-20 16:09 ` Mike Snitzer
2017-12-18 17:28 ` [PATCH v4 2/2] dm-unstripe: Add documentation for unstripe target Scott Bauer
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=20171218193249.GA6149@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jonathan.derrick@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--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.