From: Scott Bauer <scott.bauer@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: dm-devel@redhat.com, snitzer@redhat.com, agk@redhat.com,
linux-kernel@vger.kernel.org, keith.busch@intel.com,
jonathan.derrick@intel.com
Subject: Re: [PATCH v3 2/2] dm unstripe: Add documentation for unstripe target
Date: Wed, 13 Dec 2017 16:58:30 -0700 [thread overview]
Message-ID: <20171213235829.tr62tyc3u2v77yp6@sbauer-Z170X-UD5> (raw)
In-Reply-To: <808cd141-3c0a-d0ae-5b9d-efc19ab9f0fb@infradead.org>
On Wed, Dec 13, 2017 at 04:18:06PM -0800, Randy Dunlap wrote:
> Use ASCII characters ___ or ---, not whatever those bottom block characters are.
Argh, sorry, I removed those for an internal review but forgot to remove them here.
>
> > +
> > + The purpose of this unstriping is to provide better QoS in noisy
> > + neighbor environments. When two partitions are created on the
> > + aggregate drive without this unstriping, reads on one partition
> > + can affect writes on another partition. This is because the partitions
> > + are striped across the two cores. When we unstripe this hardware RAID 0
> > + and make partitions on each new exposed device the two partitions are now
> > + physically separated.
> > +
> > + With the module we were able to segregate a fio script that has read and
> > + write jobs that are independent of each other. Compared to when we run
> > + the test on a combined drive with partitions, we were able to get a 92%
> > + reduction in five-9ths read latency using this device mapper target.
>
> 5/9ths
> although I can't quite parse that sentence.
I'll reword it, thanks.
prev parent reply other threads:[~2017-12-14 0:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 21:33 [PATCH v3 0/2] dm-unstripe Scott Bauer
2017-12-13 21:33 ` [PATCH v3 1/2] dm-unstripe: unstripe RAID 0/dm-striped device Scott Bauer
2017-12-14 0:11 ` Randy Dunlap
2017-12-15 15:27 ` Scott Bauer
2017-12-15 19:55 ` Randy Dunlap
2017-12-13 21:33 ` [PATCH v3 2/2] dm unstripe: Add documentation for unstripe target Scott Bauer
2017-12-14 0:18 ` Randy Dunlap
2017-12-13 23:58 ` Scott Bauer [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=20171213235829.tr62tyc3u2v77yp6@sbauer-Z170X-UD5 \
--to=scott.bauer@intel.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=snitzer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®