From: "Matias Bjørling" <mb@lightnvm.io>
To: igor.j.konopko@intel.com, marcin.dziegielewski@intel.com,
javier@cnexlabs.com, hans.holmberg@cnexlabs.com, hlitz@ucsc.edu,
youngtack.jin@circuitblvd.com
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
"Matias Bjørling" <mb@lightnvm.io>
Subject: [RFC PATCH v2 0/1] lightnvm: move bad block and chunk state logic to core
Date: Thu, 16 Aug 2018 13:34:16 +0200 [thread overview]
Message-ID: <20180816113417.3641-1-mb@lightnvm.io> (raw)
This patch moves the 1.2 and 2.0 block/chunk metadata retrieval to
core.
Hi Javier, I did not end up using your patch. I had misunderstood what
was implemented. Instead I implemented the detection of the each chunk by
first sensing the first page, then the last page, and if the chunk
is sensed as open, a per page scan will be executed to update the write
pointer appropriately.
Note that one needs a real drive to test the implementation. The 1.2
qemu implementation is lacking. I did update it a bit, such that
it defaults to all blocks being free. It can be picked up in the ocssd
qemu repository.
Changes since v1:
- Add sensing of chunks wrt to free/open/closed
- Add update of write pointer if chunk state is open
Matias Bjørling (1):
lightnvm: move bad block and chunk state logic to core
drivers/lightnvm/core.c | 310 +++++++++++++++++++++++++++++++++++--------
drivers/lightnvm/pblk-core.c | 6 +-
drivers/lightnvm/pblk-init.c | 116 +---------------
drivers/lightnvm/pblk.h | 2 +-
drivers/nvme/host/lightnvm.c | 4 +-
include/linux/lightnvm.h | 15 +--
6 files changed, 266 insertions(+), 187 deletions(-)
--
2.11.0
next reply other threads:[~2018-08-16 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 11:34 Matias Bjørling [this message]
2018-08-16 11:34 ` [RFC PATCH v2 1/1] " Matias Bjørling
2018-08-16 15:53 ` [RFC PATCH v2 0/1] " Javier Gonzalez
2018-08-17 8:21 ` Matias Bjørling
2018-08-17 8:44 ` Javier Gonzalez
2018-08-17 9:29 ` Matias Bjørling
2018-08-17 9:34 ` Javier Gonzalez
2018-08-17 9:42 ` Matias Bjørling
2018-08-17 10:49 ` Javier Gonzalez
2018-08-17 10:57 ` Matias Bjørling
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=20180816113417.3641-1-mb@lightnvm.io \
--to=mb@lightnvm.io \
--cc=hans.holmberg@cnexlabs.com \
--cc=hlitz@ucsc.edu \
--cc=igor.j.konopko@intel.com \
--cc=javier@cnexlabs.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.dziegielewski@intel.com \
--cc=youngtack.jin@circuitblvd.com \
/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®