LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Matias Bjørling" <mb@lightnvm.io>
To: Hans Holmberg <hans.ml.holmberg@owltronix.com>
Cc: linux-block@vger.kernel.org,
Javier Gonzales <javier@cnexlabs.com>,
linux-kernel@vger.kernel.org,
Hans Holmberg <hans.holmberg@cnexlabs.com>
Subject: Re: [PATCH v2 0/3] Rework write error handling in pblk
Date: Sat, 28 Apr 2018 12:31:08 -0700 [thread overview]
Message-ID: <7536f5dc-bc11-ae4b-b11e-9c3995142cd0@lightnvm.io> (raw)
In-Reply-To: <1524548732-4326-1-git-send-email-hans.ml.holmberg@owltronix.com>
On 4/23/18 10:45 PM, Hans Holmberg wrote:
> From: Hans Holmberg <hans.holmberg@cnexlabs.com>
>
> This patch series fixes the(currently incomplete) write error handling
> in pblk by:
>
> * queuing and re-submitting failed writes in the write buffer
> * evacuating valid data data in lines with write failures, so the
> chunk(s) with write failures can be reset to a known state by the fw
>
> Lines with failures in smeta are put back on the free list.
> Failed chunks will be reset on the next use.
>
> If a write failes in emeta, the lba list is cached so the line can be
> garbage collected without scanning the out-of-band area.
>
> Changes in V2:
> - Added the recov_writes counter increase to the new path
> - Moved lba list emeta reading during gc to a separate function
> - Allocating the saved lba list with pblk_malloc instead of kmalloc
> - Fixed formatting issues
> - Removed dead code
>
> Hans Holmberg (3):
> lightnvm: pblk: rework write error recovery path
> lightnvm: pblk: garbage collect lines with failed writes
> lightnvm: pblk: fix smeta write error path
>
> drivers/lightnvm/pblk-core.c | 52 +++++++-
> drivers/lightnvm/pblk-gc.c | 102 +++++++++------
> drivers/lightnvm/pblk-init.c | 47 ++++---
> drivers/lightnvm/pblk-rb.c | 39 ------
> drivers/lightnvm/pblk-recovery.c | 91 -------------
> drivers/lightnvm/pblk-rl.c | 29 ++++-
> drivers/lightnvm/pblk-sysfs.c | 15 ++-
> drivers/lightnvm/pblk-write.c | 269 ++++++++++++++++++++++++++-------------
> drivers/lightnvm/pblk.h | 36 ++++--
> 9 files changed, 384 insertions(+), 296 deletions(-)
>
Thanks Hans. I've applied 1 & 3. The second did not apply cleanly to
for-4.18/core. Could you please resend a rebased version?
next prev parent reply other threads:[~2018-04-28 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 5:45 Hans Holmberg
2018-04-24 5:45 ` [PATCH v2 1/3] lightnvm: pblk: rework write error recovery path Hans Holmberg
2018-04-30 9:13 ` Javier Gonzalez
2018-04-24 5:45 ` [PATCH v2 2/3] lightnvm: pblk: garbage collect lines with failed writes Hans Holmberg
2018-04-30 9:14 ` Javier Gonzalez
2018-04-30 9:19 ` Javier Gonzalez
2018-04-24 5:45 ` [PATCH v2 3/3] lightnvm: pblk: fix smeta write error path Hans Holmberg
2018-04-30 9:19 ` Javier Gonzalez
2018-04-28 19:31 ` Matias Bjørling [this message]
2018-04-30 9:11 ` [PATCH v2 0/3] Rework write error handling in pblk Javier Gonzalez
2018-05-07 13:05 ` Matias Bjørling
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=7536f5dc-bc11-ae4b-b11e-9c3995142cd0@lightnvm.io \
--to=mb@lightnvm.io \
--cc=hans.holmberg@cnexlabs.com \
--cc=hans.ml.holmberg@owltronix.com \
--cc=javier@cnexlabs.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [PATCH v2 0/3] Rework write error handling in pblk' \
/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
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).