mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Javier Gonzalez <javier@cnexlabs.com>
To: "Javier González" <jg@lightnvm.io>
Cc: "mb@lightnvm.io" <mb@lightnvm.io>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] lightnvm: simplify geometry structure.
Date: Tue, 27 Feb 2018 16:09:59 +0000	[thread overview]
Message-ID: <A1101358-5262-4AE5-B486-83344B99A7AD@cnexlabs.com> (raw)
In-Reply-To: <1519747032-25704-2-git-send-email-javier@cnexlabs.com>


> On 27 Feb 2018, at 16.57, Javier González <jg@lightnvm.io> wrote:
> 
> Currently, the device geometry is stored redundantly in the nvm_id and
> nvm_geo structures at a device level. Moreover, when instantiating
> targets on a specific number of LUNs, these structures are replicated
> and manually modified to fit the instance channel and LUN partitioning.
> 
> Instead, create a generic geometry around nvm_geo, which can be used by
> (i) the underlying device to describe the geometry of the whole device,
> and (ii) instances to describe their geometry independently.
> 
> Since these share a big part of the geometry, create a nvm_common_geo
> structure that keeps the static geoometry values that are shared across
> instances.
> 
> As we introduce support for 2.0, these structures allow to abstract
> spec. specific values and present a common geometry to targets.
> 
> Signed-off-by: Javier González <javier@cnexlabs.com>
> ---
> 

Please ignore this commit message for now. It’s not updated...

Javier

  reply	other threads:[~2018-02-27 16:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 15:57 [PATCH V4] " Javier González
2018-02-27 15:57 ` [PATCH] " Javier González
2018-02-27 16:09   ` Javier Gonzalez [this message]
2018-02-27 18:23   ` Matias Bjørling
2018-02-27 19:27     ` 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=A1101358-5262-4AE5-B486-83344B99A7AD@cnexlabs.com \
    --to=javier@cnexlabs.com \
    --cc=jg@lightnvm.io \
    --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®