public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matias Bjørling" <mb@lightnvm.io>
To: "Javier González" <jg@lightnvm.io>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	"Javier González" <javier@cnexlabs.com>
Subject: Re: [PATCH] lightnvm: do not load L2P table if not supported
Date: Wed, 2 Mar 2016 19:53:55 +0100	[thread overview]
Message-ID: <56D736C3.6070109@lightnvm.io> (raw)
In-Reply-To: <1456932094-9808-1-git-send-email-javier@javigon.com>

On 03/02/2016 04:21 PM, Javier González wrote:
> An Open-Channel SSD can work on two modes: (i) hybrid mode, where the
> L2P table is maintained both by the host and by the device; and (ii)
> full host-based, where the L2P table is uniquely maintained by the host.
> The current rrpc target operates on hybrid mode.
>
> In the advent of a new target implementing the full host-based mode, do
> not assume that the L2P table must be loaded on the generic media
> manager; check device properties loaded on the identify command instead.
>
> Signed-off-by: Javier González <javier@cnexlabs.com>
> ---
>   drivers/lightnvm/gennvm.c | 3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/drivers/lightnvm/gennvm.c b/drivers/lightnvm/gennvm.c
> index 42c1c2a..0625d42 100644
> --- a/drivers/lightnvm/gennvm.c
> +++ b/drivers/lightnvm/gennvm.c
> @@ -257,6 +257,9 @@ static int gennvm_blocks_init(struct nvm_dev *dev, struct gen_nvm *gn)
>   		}
>   	}
>
> +	if (!(dev->identity.dom & NVM_RSP_L2P))
> +		return 0;
> +
>   	if (dev->ops->get_l2p_tbl) {
>   		ret = dev->ops->get_l2p_tbl(dev, 0, dev->total_secs,
>   							gennvm_block_map, dev);
>

Thanks, applied for 4.6.

      reply	other threads:[~2016-03-02 18:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 15:21 [PATCH] lightnvm: do not load L2P table if not supported Javier González
2016-03-02 18:53 ` 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=56D736C3.6070109@lightnvm.io \
    --to=mb@lightnvm.io \
    --cc=javier@cnexlabs.com \
    --cc=jg@lightnvm.io \
    --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