From: "Javier González" <jg@lightnvm.io>
To: mb@lightnvm.io, axboe@fb.com
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
"Javier González" <javier@cnexlabs.com>
Subject: [PATCH 00/10] lightnvm: pblk fixes for 4.13
Date: Fri, 30 Jun 2017 17:56:33 +0200 [thread overview]
Message-ID: <1498838203-21539-1-git-send-email-javier@cnexlabs.com> (raw)
Hi Jens,
Here you have a second round of fixes for pblk. They are in essence bug
fixes including a double-free reported by Dan.
There is also regression fix for pblk removal, which was introduced with
the new metadata scheduler. This fix makes that removing a pblk instance
takes again at most 2 seconds.
Finally, I also included a patch for double checking the L2P to verify a
cache hit before reading from the write cache. We have experienced a
database not issuing fsync before reading recently written metadata
triggering a bad cache read. We verified it this week. This patch is an
easy fix that we can make in pblk.
The patches apply on top of your for-4.13/block and can be found at:
https://github.com/OpenChannelSSD pblk.for-4.13
Please pull.
Thanks,
Javier
Javier González (10):
lightnvm: pblk: fix bad le64 assignations
lightnvm: pblk: fix double-free on pblk init
lightnvm: pblk: remove unused return variable
lightnvm: pblk: schedule if data is not ready
lightnvm: pblk: use right metadata buffer for recovery
lightnvm: pblk: use vmalloc for GC data buffer
lightnvm: pblk: remove target using async. I/Os
lightnvm: pblk: add initialization check
lightnvm: pblk: verify that cache read is still valid
lightnvm: pblk: set line bitmap check under debug
drivers/lightnvm/pblk-core.c | 21 +++--
drivers/lightnvm/pblk-gc.c | 11 ++-
drivers/lightnvm/pblk-init.c | 17 +++-
drivers/lightnvm/pblk-map.c | 2 +-
drivers/lightnvm/pblk-rb.c | 27 +++++-
drivers/lightnvm/pblk-read.c | 7 +-
drivers/lightnvm/pblk-recovery.c | 173 ++++++++++++++++++++++-----------------
drivers/lightnvm/pblk-sysfs.c | 4 +-
drivers/lightnvm/pblk-write.c | 5 +-
drivers/lightnvm/pblk.h | 22 ++++-
10 files changed, 184 insertions(+), 105 deletions(-)
--
2.7.4
next reply other threads:[~2017-06-30 15:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 15:56 Javier González [this message]
2017-06-30 15:56 ` [PATCH 01/10] lightnvm: pblk: fix bad le64 assignations Javier González
2017-06-30 15:56 ` [PATCH 02/10] lightnvm: pblk: fix double-free on pblk init Javier González
2017-06-30 15:56 ` [PATCH 03/10] lightnvm: pblk: remove unused return variable Javier González
2017-06-30 15:56 ` [PATCH 04/10] lightnvm: pblk: schedule if data is not ready Javier González
2017-06-30 15:56 ` [PATCH 05/10] lightnvm: pblk: use right metadata buffer for recovery Javier González
2017-06-30 15:56 ` [PATCH 06/10] lightnvm: pblk: use vmalloc for GC data buffer Javier González
2017-06-30 15:56 ` [PATCH 07/10] lightnvm: pblk: remove target using async. I/Os Javier González
2017-06-30 15:56 ` [PATCH 08/10] lightnvm: pblk: add initialization check Javier González
2017-06-30 15:56 ` [PATCH 09/10] lightnvm: pblk: verify that cache read is still valid Javier González
2017-06-30 15:56 ` [PATCH 10/10] lightnvm: pblk: set line bitmap check under debug Javier González
2017-06-30 17:08 ` [PATCH 00/10] lightnvm: pblk fixes for 4.13 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=1498838203-21539-1-git-send-email-javier@cnexlabs.com \
--to=jg@lightnvm.io \
--cc=axboe@fb.com \
--cc=javier@cnexlabs.com \
--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®