From: "Matias Bjørling" <mb@lightnvm.io>
To: linux-block@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
javier@cnexlabs.com, "Matias Bjørling" <mb@lightnvm.io>
Subject: [PATCH v2 0/6] lightnvm: base 2.0 implementation
Date: Thu, 15 Feb 2018 14:11:54 +0100 [thread overview]
Message-ID: <20180215131200.3354-1-mb@lightnvm.io> (raw)
A couple of patches for 2.0 support for the lightnvm subsystem. They
form the foundation for the integration.
The first two patches is preparation for the 2.0 work. The third patch
implements the 2.0 data structures, the geometry command, and exposes
the sysfs attributes that comes with the 2.0 specification. Note that
the attributes between 1.2 and 2.0 are different, and it is expected
that user-space shall use the version sysfs attribute to know which
attributes will be available.
The next two patches removes max_phys_sect and max_rq_size, as they
not used.
The last patch implements support for using the nvme namespace logical
block and metadata fields and sync it with the internal lightnvm
identify structures.
Changes since v2:
- Removed blk_queue_block_size() setup in nvm_init and made sure
to only update csecs and sos in on the late setup path. No reason
to set it twice. From discussion with Javier.
- Added two extra patches, that removes max_phys_sect and
max_rq_size.
Changes since v1:
- pr_err fix from Randy.
- Address type fix from Javier.
- Also CC the nvme mailing list.
Matias Bjørling (6):
lightnvm: make 1.2 data structures explicit
lightnvm: flatten nvm_id_group into nvm_id
lightnvm: add 2.0 geometry identification
lightnvm: remove max_rq_size
lightnvm: remove nvm_dev_ops->max_phys_sect
nvme: lightnvm: add late setup of block size and metadata
drivers/lightnvm/core.c | 61 ++---
drivers/lightnvm/pblk-init.c | 9 +-
drivers/lightnvm/pblk-recovery.c | 8 +-
drivers/nvme/host/core.c | 2 +
drivers/nvme/host/lightnvm.c | 513 ++++++++++++++++++++++++++++-----------
drivers/nvme/host/nvme.h | 2 +
include/linux/lightnvm.h | 71 +++---
7 files changed, 442 insertions(+), 224 deletions(-)
--
2.11.0
next reply other threads:[~2018-02-15 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 13:11 Matias Bjørling [this message]
2018-02-15 13:11 ` [PATCH v2 1/6] lightnvm: make 1.2 data structures explicit Matias Bjørling
2018-02-15 13:11 ` [PATCH v2 2/6] lightnvm: flatten nvm_id_group into nvm_id Matias Bjørling
2018-02-15 13:11 ` [PATCH v2 3/6] lightnvm: add 2.0 geometry identification Matias Bjørling
2018-02-15 13:11 ` [PATCH v2 4/6] lightnvm: remove max_rq_size Matias Bjørling
2018-02-15 13:11 ` [PATCH v2 5/6] lightnvm: remove nvm_dev_ops->max_phys_sect Matias Bjørling
2018-02-16 6:48 ` Javier Gonzalez
2018-02-19 7:31 ` Matias Bjørling
2018-02-19 11:05 ` Javier Gonzalez
2018-02-15 13:12 ` [PATCH v2 6/6] nvme: lightnvm: add late setup of block size and metadata Matias Bjørling
2018-02-21 9:35 ` [PATCH v2 0/6] lightnvm: base 2.0 implementation 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=20180215131200.3354-1-mb@lightnvm.io \
--to=mb@lightnvm.io \
--cc=javier@cnexlabs.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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).