mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Matias Bjørling" <mb@lightnvm.io>
To: Javier Gonzalez <javier@cnexlabs.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] lightnvm: base 2.0 implementation
Date: Thu, 8 Feb 2018 10:42:44 +0100	[thread overview]
Message-ID: <8b50ed33-226a-760a-e888-51ff573b9557@lightnvm.io> (raw)
In-Reply-To: <DA4E2087-F1E8-4903-9B53-95CFECD6B868@cnexlabs.com>

On 02/08/2018 10:35 AM, Javier Gonzalez wrote:
>> On 5 Feb 2018, at 13.15, Matias Bjørling <mb@lightnvm.io> wrote:
>>
>> Hi,
>>
>> A couple of patches for 2.0 support for the lightnvm subsystem. They
>> form the basis for integrating 2.0 support.
>>
>> For the rest of the support, Javier has code that implements report
>> chunk and sets up the LBA format data structure. He also has a bunch
>> of patches that brings pblk up to speed.
>>
>> 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 last patch implements support for using the nvme namespace logical
>> block and metadata fields and sync it with the internal lightnvm
>> identify structures.
>>
>> -Matias
>>
>> Matias Bjørling (4):
>>   lightnvm: make 1.2 data structures explicit
>>   lightnvm: flatten nvm_id_group into nvm_id
>>   lightnvm: add 2.0 geometry identification
>>   nvme: lightnvm: add late setup of block size and metadata
>>
>> drivers/lightnvm/core.c      |  27 ++-
>> drivers/nvme/host/core.c     |   2 +
>> drivers/nvme/host/lightnvm.c | 508 ++++++++++++++++++++++++++++++++-----------
>> drivers/nvme/host/nvme.h     |   2 +
>> include/linux/lightnvm.h     |  64 +++---
>> 5 files changed, 426 insertions(+), 177 deletions(-)
>>
>> --
>> 2.11.0
> 
> Thanks for posting these. I have started rebasing my patches on top of
> the new geometry - it is a bit different of how I implemented it, but
> I'll take care of it.
> 
> I'll review as I go - some of the changes I have might make sense to
> squash in your patches to keep a clean history...
> 

Thanks.

> I'll add a couple of patches abstracting the geometry so that at core.c
> level we only work with a single geometry structure. This is they way it
> is done in the early patches I pointe you to before. Then it is patches
> building bottom-up support for the new features in 2.0.
> 

Yep, I was expecting that. I skipped that part since it went into pblk 
and you already had some patches for it.

> Javier
> 

      reply	other threads:[~2018-02-08  9:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 12:15 Matias Bjørling
2018-02-05 12:15 ` [PATCH 1/4] lightnvm: make 1.2 data structures explicit Matias Bjørling
2018-02-05 12:15 ` [PATCH 2/4] lightnvm: flatten nvm_id_group into nvm_id Matias Bjørling
2018-02-05 12:15 ` [PATCH 3/4] lightnvm: add 2.0 geometry identification Matias Bjørling
2018-02-05 18:04   ` Randy Dunlap
2018-02-06  9:43     ` Matias Bjørling
2018-02-08 13:35   ` Javier Gonzalez
2018-02-05 12:15 ` [PATCH 4/4] nvme: lightnvm: add late setup of block size and metadata Matias Bjørling
2018-03-23 11:00   ` Matias Bjørling
2018-03-28  8:28     ` Christoph Hellwig
2018-03-28 12:36       ` Matias Bjørling
2018-02-08  9:35 ` [PATCH 0/4] lightnvm: base 2.0 implementation Javier Gonzalez
2018-02-08  9:42   ` 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=8b50ed33-226a-760a-e888-51ff573b9557@lightnvm.io \
    --to=mb@lightnvm.io \
    --cc=javier@cnexlabs.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®