From: "Matias Bjørling" <mb@lightnvm.io>
To: axboe@fb.com
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
"Matias Bjørling" <mb@lightnvm.io>
Subject: [GIT PULL 00/20] lightnvm updates for 4.18
Date: Mon, 28 May 2018 10:58:21 +0200 [thread overview]
Message-ID: <20180528085841.26684-1-mb@lightnvm.io> (raw)
Hi Jens,
Please pick up the following patches.
- Hans reworked the write error recovery path in pblk.
- Igor added extra error handling for lines, and fixed a bug in the
pblk ringbuffer during GC.
- Javier refactored the pblk code a bit, added extra error
handling, and added checks to verify that data returned from drive
is appropriate.
- Marcin added some extra logic to manage the write buffer. Now
MW_CUNITS can be zero and the size of write buffer can be changed
at module load time.
Thanks,
Matias
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
Igor Konopko (4):
lightnvm: proper error handling for pblk_bio_add_pages
lightnvm: error handling when whole line is bad
lightnvm: fix partial read error path
lightnvm: pblk: sync RB and RL states during GC
Javier González (11):
lightnvm: pblk: fail gracefully on line alloc. failure
lightnvm: pblk: recheck for bad lines at runtime
lightnvm: pblk: check read lba on gc path
lightnvn: pblk: improve error msg on corrupted LBAs
lightnvm: pblk: warn in case of corrupted write buffer
lightnvm: pblk: return NVM_ error on failed submission
lightnvm: pblk: remove unnecessary indirection
lightnvm: pblk: remove unnecessary argument
lightnvm: pblk: check for chunk size before allocating it
lightnvn: pass flag on graceful teardown to targets
lightnvm: pblk: remove dead function
Marcin Dziegielewski (2):
lightnvm: pblk: handle case when mw_cunits equals to 0
lightnvm: pblk: add possibility to set write buffer size manually
drivers/lightnvm/core.c | 10 +-
drivers/lightnvm/pblk-core.c | 149 +++++++++++++++------
drivers/lightnvm/pblk-gc.c | 112 ++++++++++------
drivers/lightnvm/pblk-init.c | 112 +++++++++++-----
drivers/lightnvm/pblk-map.c | 33 +++--
drivers/lightnvm/pblk-rb.c | 51 +------
drivers/lightnvm/pblk-read.c | 83 +++++++++---
drivers/lightnvm/pblk-recovery.c | 91 -------------
drivers/lightnvm/pblk-rl.c | 29 +++-
drivers/lightnvm/pblk-sysfs.c | 15 ++-
drivers/lightnvm/pblk-write.c | 281 +++++++++++++++++++++++++--------------
drivers/lightnvm/pblk.h | 43 +++---
drivers/nvme/host/lightnvm.c | 1 -
include/linux/lightnvm.h | 2 +-
14 files changed, 604 insertions(+), 408 deletions(-)
--
2.11.0
next reply other threads:[~2018-05-28 8:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 8:58 Matias Bjørling [this message]
2018-05-28 8:58 ` [GIT PULL 01/20] lightnvm: pblk: fail gracefully on line alloc. failure Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 02/20] lightnvm: pblk: recheck for bad lines at runtime Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 03/20] lightnvm: pblk: check read lba on gc path Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 04/20] lightnvm: pblk: improve error msg on corrupted LBAs Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 05/20] lightnvm: pblk: warn in case of corrupted write buffer Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 06/20] lightnvm: pblk: return NVM_ error on failed submission Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 07/20] lightnvm: pblk: remove unnecessary indirection Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 08/20] lightnvm: pblk: remove unnecessary argument Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 09/20] lightnvm: pblk: check for chunk size before allocating it Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 10/20] lightnvm: pass flag on graceful teardown to targets Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 11/20] lightnvm: pblk: remove dead function Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 12/20] lightnvm: pblk: rework write error recovery path Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 13/20] lightnvm: pblk: garbage collect lines with failed writes Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 14/20] lightnvm: pblk: fix smeta write error path Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 15/20] lightnvm: proper error handling for pblk_bio_add_pages Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 16/20] lightnvm: error handling when whole line is bad Matias Bjørling
2018-05-28 10:59 ` Javier Gonzalez
2018-05-29 13:15 ` Konopko, Igor J
2018-05-29 18:29 ` Javier Gonzalez
2018-05-28 8:58 ` [GIT PULL 17/20] lightnvm: fix partial read error path Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 18/20] lightnvm: pblk: handle case when mw_cunits equals to 0 Matias Bjørling
2018-05-28 11:02 ` Javier Gonzalez
2018-06-04 10:09 ` Dziegielewski, Marcin
2018-06-04 10:21 ` Javier Gonzalez
2018-06-04 11:11 ` Dziegielewski, Marcin
2018-06-04 11:15 ` Javier Gonzalez
2018-06-04 17:17 ` Dziegielewski, Marcin
2018-06-05 7:12 ` Javier Gonzalez
2018-06-05 9:18 ` Dziegielewski, Marcin
2018-05-28 8:58 ` [GIT PULL 19/20] lightnvm: pblk: add possibility to set write buffer size manually Matias Bjørling
2018-05-28 8:58 ` [GIT PULL 20/20] lightnvm: pblk: sync RB and RL states during GC Matias Bjørling
2018-05-28 10:51 ` Javier Gonzalez
2018-05-29 13:07 ` Konopko, Igor J
2018-05-29 17:58 ` Javier Gonzalez
2018-06-01 10:45 ` [GIT PULL 00/20] lightnvm updates for 4.18 Matias Bjørling
2018-06-01 12:36 ` Jens Axboe
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=20180528085841.26684-1-mb@lightnvm.io \
--to=mb@lightnvm.io \
--cc=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).