From: "Matias Bjørling" <mb@lightnvm.io>
To: Igor Konopko <igor.j.konopko@intel.com>,
javier@javigon.com, hans.holmberg@cnexlabs.com
Cc: linux-block@vger.kernel.org
Subject: Re: [PATCH v2 0/8] lightnvm: bugfixes and improvements
Date: Sat, 9 Mar 2019 17:56:44 +0100 [thread overview]
Message-ID: <eda5d77a-2677-4409-d8a7-b67071f4e47e@lightnvm.io> (raw)
In-Reply-To: <20190305135120.29284-1-igor.j.konopko@intel.com>
On 3/5/19 2:51 PM, Igor Konopko wrote:
> This series provides a group of the bugfixes or improvements
> for lightnvm and pblk device.
>
> Most of the patches are rather simple and covers some corner cases
> scenario, but we were able to hit most of them in some scenarios.
> Few others close some existing gaps which we were able to found.
>
> Changes v2->v1:
> -skipped patches which were applied in v1
> -dropped not needed patch for pblk_should_kick_write()
> -patch which scan for opened chunks on pblk creation do not close
> chunk anymore, just print the warning
> -unknown read errors are counted seperately from read unrecoverable
>
> Igor Konopko (8):
> lightnvm: pblk: Gracefully handle GC vmalloc fail
> lightnvm: pblk: Fix put line back behaviour
> lightnvm: pblk: Count all read errors in stats
> lightnvm: pblk: Ensure that erase is chunk aligned
> lightnvm: pblk: Cleanly fail when there is not enough memory
> lightnvm: pblk: Set proper read stutus in bio
> lightnvm: pblk: warn about opened chunk on factory init
> lightnvm: Inherit mdts from the parent nvme device
>
> drivers/lightnvm/core.c | 9 +++++++--
> drivers/lightnvm/pblk-core.c | 15 +++++++++++++++
> drivers/lightnvm/pblk-gc.c | 35 +++++++++++++++++++----------------
> drivers/lightnvm/pblk-init.c | 24 +++++++++++++++++++-----
> drivers/lightnvm/pblk-map.c | 1 +
> drivers/lightnvm/pblk-read.c | 11 +++++------
> drivers/lightnvm/pblk-sysfs.c | 3 ++-
> drivers/lightnvm/pblk.h | 2 ++
> drivers/nvme/host/lightnvm.c | 1 +
> include/linux/lightnvm.h | 1 +
> 10 files changed, 72 insertions(+), 30 deletions(-)
>
Thanks Igor. Thanks Javier and Hans for the reviews.
I've picked up 1, 2, 4, 5, 6, and 8. Note that I've lower-cased the
first letter after "lightnvm: pblk:" in the patches, and also updated
the wording a bit when appropriate.
prev parent reply other threads:[~2019-03-09 16:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 13:51 [PATCH v2 0/8] lightnvm: bugfixes and improvements Igor Konopko
2019-03-05 13:51 ` [PATCH v2 1/8] lightnvm: pblk: Gracefully handle GC vmalloc fail Igor Konopko
2019-03-06 14:09 ` Hans Holmberg
2019-03-05 13:51 ` [PATCH v2 2/8] lightnvm: pblk: Fix put line back behaviour Igor Konopko
2019-03-05 13:51 ` [PATCH v2 3/8] lightnvm: pblk: Count all read errors in stats Igor Konopko
2019-03-06 7:28 ` Javier González
2019-03-06 14:19 ` Hans Holmberg
2019-03-06 14:22 ` Igor Konopko
2019-03-05 13:51 ` [PATCH v2 4/8] lightnvm: pblk: Ensure that erase is chunk aligned Igor Konopko
2019-03-06 7:28 ` Javier González
2019-03-06 14:20 ` Hans Holmberg
2019-03-05 13:51 ` [PATCH v2 5/8] lightnvm: pblk: Cleanly fail when there is not enough memory Igor Konopko
2019-03-06 14:20 ` Hans Holmberg
2019-03-05 13:51 ` [PATCH v2 6/8] lightnvm: pblk: Set proper read stutus in bio Igor Konopko
2019-03-06 8:00 ` Javier González
2019-03-06 14:23 ` Hans Holmberg
2019-03-05 13:51 ` [PATCH v2 7/8] lightnvm: pblk: warn about opened chunk on factory init Igor Konopko
2019-03-06 7:43 ` Javier González
2019-03-06 14:27 ` Hans Holmberg
2019-03-06 14:31 ` Igor Konopko
2019-03-05 13:51 ` [PATCH v2 8/8] lightnvm: Inherit mdts from the parent nvme device Igor Konopko
2019-03-05 14:34 ` Matias Bjørling
2019-03-06 7:44 ` Javier González
2019-03-06 14:29 ` Hans Holmberg
2019-03-09 16:56 ` Matias Bjørling [this message]
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=eda5d77a-2677-4409-d8a7-b67071f4e47e@lightnvm.io \
--to=mb@lightnvm.io \
--cc=hans.holmberg@cnexlabs.com \
--cc=igor.j.konopko@intel.com \
--cc=javier@javigon.com \
--cc=linux-block@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