linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shaohua Li <shli@kernel.org>
To: Pawel Baldysiak <pawel.baldysiak@intel.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 0/2] md: Add support for Multiple PPLs
Date: Fri, 25 Aug 2017 14:53:00 -0700	[thread overview]
Message-ID: <20170825215300.xgkdklgi4lxvhxrx@kernel.org> (raw)
In-Reply-To: <c9d77b2c-f1ab-bcce-5441-5b8fa9bede13@intel.com>

On Fri, Aug 25, 2017 at 10:02:07PM +0200, Pawel Baldysiak wrote:
> On 08/21/2017 06:14 PM, Shaohua Li wrote> Can you elaborate more?
> > 
> Storage presented to the host may have a RAID on the back-end. For NVMe
> SSDs, the 1.3 specification provided a field to advertise chunk
> boundaries: Identify Namespace NOIOB. We need to span the entire stripe
> to utilize the total available capacity, otherwise we'll repeatedly
> write to only a subset, increasing write amplification factor. The new
> PPL approach is designed to access the full capacity.

Ok, this makes sense. The 1MB area looks arbitrary though. What if the
chunk is 2MB? Could we make it configurable?

Thanks,
Shaohua

  reply	other threads:[~2017-08-25 21:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16 15:13 [PATCH 0/2] md: Add support for Multiple PPLs Pawel Baldysiak
2017-08-16 15:13 ` [PATCH 1/2] md: Runtime support for multiple ppls Pawel Baldysiak
2017-08-16 15:13 ` [PATCH 2/2] raid5-ppl: Recovery support for multiple partial parity logs Pawel Baldysiak
2017-08-17 18:03 ` [PATCH 0/2] md: Add support for Multiple PPLs Shaohua Li
2017-08-21 14:54   ` Pawel Baldysiak
2017-08-21 16:14     ` Shaohua Li
2017-08-25 20:02       ` Pawel Baldysiak
2017-08-25 21:53         ` Shaohua Li [this message]
2017-08-28  7:44           ` Artur Paszkiewicz
2017-08-28 14:54             ` Shaohua Li

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=20170825215300.xgkdklgi4lxvhxrx@kernel.org \
    --to=shli@kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=pawel.baldysiak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).