From: Jens Axboe <axboe@kernel.dk>
To: "Javier González" <jg@lightnvm.io>
Cc: mb@lightnvm.io, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Javier González" <javier@cnexlabs.com>
Subject: Re: [PATCH 00/20] LightNVM: pblk patches for 4.13
Date: Mon, 26 Jun 2017 16:29:21 -0600 [thread overview]
Message-ID: <20170626222920.GA9175@kernel.dk> (raw)
In-Reply-To: <1498471049-25505-1-git-send-email-javier@cnexlabs.com>
On Mon, Jun 26 2017, Javier Gonz�lez wrote:
> Hi Matias,
>
> Here you have the pblk patchset for this window.
>
> Apart from small fixes for LightNVM core and pblk, there are three
> relevant changes:
>
> - Metadata for each line is no longer issued on a separate workqueue,
> but instead, all I/Os are scheduled on the write thread. This allows
> to have more control over LUN collisions. The result is that we can
> use the full bandwidth of the device for user data. In the 4.12 pblk,
> we use ~25% of the bandwidth for metadata.
>
> - The rate-limiter and GC have been tuned to keep the GC writer busy.
> Also, capacity per line is guaranteed for GC I/O as we reach
> capacity.
>
> - We have now a FTL state machine. This allows to fail gracefully to
> user space in case of irrecoverable errors. This state machine will
> be the base for the pblk's FTL log.
>
> The patches apply into your for-4.13/core. You can also find them in:
Nope, they do not. Patch #7 fails, because it's not on top of the
bio_set changes that went in a week or two ago. I hand applied that one,
didn't find issues with the rest.
But please remember to ensure that it applies on top of the current
branch.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: "Javier González" <jg@lightnvm.io>
Cc: mb@lightnvm.io, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Javier González" <javier@cnexlabs.com>
Subject: Re: [PATCH 00/20] LightNVM: pblk patches for 4.13
Date: Mon, 26 Jun 2017 16:29:21 -0600 [thread overview]
Message-ID: <20170626222920.GA9175@kernel.dk> (raw)
In-Reply-To: <1498471049-25505-1-git-send-email-javier@cnexlabs.com>
On Mon, Jun 26 2017, Javier González wrote:
> Hi Matias,
>
> Here you have the pblk patchset for this window.
>
> Apart from small fixes for LightNVM core and pblk, there are three
> relevant changes:
>
> - Metadata for each line is no longer issued on a separate workqueue,
> but instead, all I/Os are scheduled on the write thread. This allows
> to have more control over LUN collisions. The result is that we can
> use the full bandwidth of the device for user data. In the 4.12 pblk,
> we use ~25% of the bandwidth for metadata.
>
> - The rate-limiter and GC have been tuned to keep the GC writer busy.
> Also, capacity per line is guaranteed for GC I/O as we reach
> capacity.
>
> - We have now a FTL state machine. This allows to fail gracefully to
> user space in case of irrecoverable errors. This state machine will
> be the base for the pblk's FTL log.
>
> The patches apply into your for-4.13/core. You can also find them in:
Nope, they do not. Patch #7 fails, because it's not on top of the
bio_set changes that went in a week or two ago. I hand applied that one,
didn't find issues with the rest.
But please remember to ensure that it applies on top of the current
branch.
--
Jens Axboe
next prev parent reply other threads:[~2017-06-26 22:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 9:57 [PATCH 00/20] LightNVM: pblk patches for 4.13 Javier González
2017-06-26 9:57 ` [PATCH 01/20] lightnvm: re-convert ppa format on I/O failure Javier González
2017-06-26 9:57 ` [PATCH 02/20] lightnvm: propagate right error code to target Javier González
2017-06-26 9:57 ` [PATCH 03/20] lightnvm: pblk: spare double cpu_to_le64 calc Javier González
2017-06-26 9:57 ` [PATCH 04/20] lightnvm: pblk: add debug stat for read cache hits Javier González
2017-06-26 9:57 ` [PATCH 05/20] lightnvm: pblk: expose max sec per write on sysfs Javier González
2017-06-26 9:57 ` [PATCH 06/20] lightnvm: pblk: generalize erase path Javier González
2017-06-26 9:57 ` [PATCH 07/20] lightnvm: pblk: rename read request pool Javier González
2017-06-26 9:57 ` [PATCH 08/20] lightnvm: pblk: sched. metadata on write thread Javier González
2017-09-20 18:28 ` Rakesh Pandit
2017-09-20 18:28 ` Rakesh Pandit
2017-09-20 19:25 ` Rakesh Pandit
2017-09-20 19:25 ` Rakesh Pandit
2017-06-26 9:57 ` [PATCH 09/20] lightnvm: pblk: delete redundant debug line stat Javier González
2017-06-26 9:57 ` [PATCH 10/20] lightnvm: pblk: delete redundant buffer pointer Javier González
2017-06-26 9:57 ` [PATCH 11/20] lightnvm: pblk: issue multiplane reads if possible Javier González
2017-06-26 9:57 ` [PATCH 12/20] lightnvm: pblk: simplify meta. memory allocation Javier González
2017-06-26 9:57 ` [PATCH 13/20] lightnvm: pblk: decouple bad block from line alloc Javier González
2017-06-26 9:57 ` [PATCH 14/20] lightnvm: pblk: choose optimal victim GC line Javier González
2017-06-26 9:57 ` [PATCH 15/20] lightnvm: pblk: set metadata list for all I/Os Javier González
2017-06-26 9:57 ` [PATCH 16/20] lightnvm: pblk: cleanup unnecessary code Javier González
2017-06-26 9:57 ` [PATCH 17/20] lightnvm: pblk: add lock assertions on helpers Javier González
2017-06-26 9:57 ` [PATCH 18/20] lightnvm: pblk: redesign GC algorithm Javier González
2017-06-26 9:57 ` [PATCH 19/20] lightnvm: pblk: set mempool and workqueue params Javier González
2017-06-26 9:57 ` [PATCH 20/20] lightnvm: pblk: fail gracefully on irrec. error Javier González
2017-06-26 22:29 ` Jens Axboe [this message]
2017-06-26 22:29 ` [PATCH 00/20] LightNVM: pblk patches for 4.13 Jens Axboe
2017-06-27 8:00 ` Javier González
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=20170626222920.GA9175@kernel.dk \
--to=axboe@kernel.dk \
--cc=javier@cnexlabs.com \
--cc=jg@lightnvm.io \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@lightnvm.io \
/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.