linux-kernel - Re: [PATCH v4 1/2] lightnvm: add non-continuous lun target creation support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1D7DBB06-093D-4F57-AE9F-E5EE43345532@lightnvm.io>
Date:	Mon, 21 Mar 2016 08:55:12 +0100
From:	Javier González <jg@...htnvm.io>
To:	Wenwei Tao <ww.tao0320@...il.com>
Cc:	Matias Bjørling <mb@...htnvm.io>,
	linux-kernel@...r.kernel.org, linux-block@...r.kernel.org
Subject: Re: [PATCH v4 1/2] lightnvm: add non-continuous lun target creation support

Hi Wenwei,

> On 19 Mar 2016, at 13:52, Wenwei Tao <ww.tao0320@...il.com> wrote:
> 
> Hi Javier
> 
> Thanks for the comment.
> I've been busy recently, so this letter is kind of late, hope you don't mind.
> I use the qemu-nvme you mentioned and configure the nvme device driver
> follow the example, it turns out the nvme device is 1 lun, I don't
> know how to configure multiple lun, so I just modify the source code
> to make it multiple lun,
> I'm not sure the modification is right, although it seems works, but
> for sake of safe I also use null_blk driver to debug this patch too.
> It turns out the target creation fail is due to wrong return value
> judgement in rrpc_luns_init().

Multiple LUN support can be found on this branch [1]. We are running
tests; we will merge it into master soon. You are welcome to use it and
send a pull-request if you see that something is missing. Please note
the new options for LightNVM on top of the hw/block/nvme.c

[1]https://github.com/OpenChannelSSD/qemu-nvme/tree/wl_sim

Javier



Download attachment "signature.asc" of type "application/pgp-signature" (843 bytes)