From: Hans Holmberg <hans.ml.holmberg@owltronix.com>
To: Matias Bjorling <mb@lightnvm.io>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Javier Gonzales <jg@lightnvm.io>,
Hans Holmberg <hans.holmberg@cnexlabs.com>
Subject: [PATCH 0/9] recovery robustness improvements
Date: Tue, 3 Oct 2017 12:05:04 +0200 [thread overview]
Message-ID: <1507025113-13351-1-git-send-email-hans.ml.holmberg@owltronix.com> (raw)
From: Hans Holmberg <hans.holmberg@cnexlabs.com>
This patchset improves the robustness of recovery - fixing a bunch of
issues that occurs when removing and re-creating a pblk instance.
It also adds a couple of debug-only prints to facilitate detection
of L2P table corruptions.
The patches apply on top of:
https://github.com/OpenChannelSSD/linux branch for-4.15/pblk
Hans Holmberg (9):
lightnvm: pblk: prevent gc kicks when gc is not operational
lightnvm: pblk: recover partially written lines correctly
lightnvm: pblk: free full lines during recovery
lightnvm: pblk: start gc if needed during init
lightnvm: pblk: consider bad sectors in emeta during recovery
lightnvm: pblk: shut down gc gracefully during exit
lightnvm: pblk: add l2p crc debug printouts
lightnvm: pblk: gc all lines in the pipeline before exit
lightnvm: pblk: correct valid lba count calculation
drivers/lightnvm/pblk-core.c | 3 ++
drivers/lightnvm/pblk-gc.c | 88 +++++++++++++++++++++++++++-------------
drivers/lightnvm/pblk-init.c | 47 ++++++++++++++++++---
drivers/lightnvm/pblk-map.c | 7 ++--
drivers/lightnvm/pblk-recovery.c | 46 ++++++++++++++-------
drivers/lightnvm/pblk-sysfs.c | 2 +-
drivers/lightnvm/pblk.h | 6 ++-
7 files changed, 145 insertions(+), 54 deletions(-)
--
2.7.4
next reply other threads:[~2017-10-03 10:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 10:05 Hans Holmberg [this message]
2017-10-03 10:05 ` [PATCH 1/9] lightnvm: pblk: prevent gc kicks when gc is not operational Hans Holmberg
2017-10-03 10:27 ` Javier González
2017-10-03 10:05 ` [PATCH 2/9] lightnvm: pblk: recover partially written lines correctly Hans Holmberg
2017-10-03 10:28 ` Javier González
2017-10-03 10:05 ` [PATCH 3/9] lightnvm: pblk: free full lines during recovery Hans Holmberg
2017-10-03 10:36 ` Javier González
2017-10-03 10:05 ` [PATCH 4/9] lightnvm: pblk: start gc if needed during init Hans Holmberg
2017-10-03 10:36 ` Javier González
2017-10-03 10:05 ` [PATCH 5/9] lightnvm: pblk: consider bad sectors in emeta during recovery Hans Holmberg
2017-10-03 10:38 ` Javier González
2017-10-03 10:05 ` [PATCH 6/9] lightnvm: pblk: shut down gc gracefully during exit Hans Holmberg
2017-10-03 10:38 ` Javier González
2017-10-03 10:05 ` [PATCH 7/9] lightnvm: pblk: add l2p crc debug printouts Hans Holmberg
2017-10-03 10:39 ` Javier González
2017-10-03 10:05 ` [PATCH 8/9] lightnvm: pblk: gc all lines in the pipeline before exit Hans Holmberg
2017-10-03 10:40 ` Javier González
2017-10-03 10:05 ` [PATCH 9/9] lightnvm: pblk: correct valid lba count calculation Hans Holmberg
2017-10-03 10:41 ` Javier González
2017-10-03 10:51 ` [PATCH 0/9] recovery robustness improvements Javier González
2017-10-03 13:53 ` Hans Holmberg
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=1507025113-13351-1-git-send-email-hans.ml.holmberg@owltronix.com \
--to=hans.ml.holmberg@owltronix.com \
--cc=hans.holmberg@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 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®