From: "Javier González" <javier@javigon.com>
To: mb@lightnvm.io
Cc: hans.holmberg@cnexlabs.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Javier González" <javier@cnexlabs.com>
Subject: [PATCH] lightnvm: pblk: recover chunk state on 1.2 devices
Date: Thu, 28 Jun 2018 11:12:00 +0200 [thread overview]
Message-ID: <1530177121-24908-1-git-send-email-javier@cnexlabs.com> (raw)
Hi Matias,
As discussed, here you have the patch reconstructing the state for 1.2
devices.
As mentioned in the patch itself, we make a tradeoff by doing this, as
writes might fail (or be more unstable) in case that a block has been
erased long before it is in used, and 1.2 does not have a way to
communicate this. The only thing the device can do is force an erase on
write when this happens, but if the device is responsible for this, one
could argue that it could prevent double-erases - which follows better
the predictability model we seek in Open-Channel.
Thoughts?
If we go this way, I will push a patch to the qemu 1.2 branch, as in the
initialization, we need to match empty page reporting with the block
metadata representing that the block is indeed erased. Ping me if you
want this patch in advance for testing.
Thanks,
Javier
Javier González (1):
lightnvm: pblk: recover chunk state on 1.2 devices
drivers/lightnvm/pblk-init.c | 138 ++++++++++++++++++++++++++++++++++++++-----
1 file changed, 124 insertions(+), 14 deletions(-)
--
2.7.4
next reply other threads:[~2018-06-28 9:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 9:12 Javier González [this message]
2018-06-28 9:12 ` [PATCH] lightnvm: pblk: recover chunk state on 1.2 devices Javier González
2018-06-29 11:14 ` Matias Bjørling
2018-06-29 11:22 ` Javier Gonzalez
2018-06-29 11:28 ` Matias Bjørling
2018-07-24 7:54 ` Javier Gonzalez
2018-08-03 11:57 ` Matias Bjørling
2018-08-03 12:02 ` Javier Gonzalez
2018-08-03 12:30 ` Matias Bjørling
2018-08-03 12:37 ` Javier Gonzalez
2018-08-03 12:46 ` Matias Bjørling
2018-08-03 12:53 ` Javier Gonzalez
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=1530177121-24908-1-git-send-email-javier@cnexlabs.com \
--to=javier@javigon.com \
--cc=hans.holmberg@cnexlabs.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