linux-kernel - Re: [RFC PATCH 2/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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACygaLDJOtYyRm+ehf-z_-tAg-S2GfBjkkE6Wp0yc+iCXacUjA@mail.gmail.com>
Date:	Thu, 21 Jan 2016 21:58:35 +0800
From:	Wenwei Tao <ww.tao0320@...il.com>
To:	Matias Bjørling <mb@...htnvm.io>
Cc:	linux-kernel@...r.kernel.org, linux-block@...r.kernel.org
Subject: Re: [RFC PATCH 2/2] lightnvm: add non-continuous lun target creation support

2016-01-21 17:49 GMT+08:00 Matias Bjørling <mb@...htnvm.io>:
> On 01/21/2016 10:47 AM, Wenwei Tao wrote:
> <snip>
>>
>> Currently a bitmap of luns already added into nvm_dev, every time we
>> map the luns we check the bitmap.
>> I don't quite understand why we need to add another bitmap?
>
> We can definitely use lun_map that you introduced in the patch.
>
Then I think the suggestion:

>How about extending the functionality to take a bitmap of luns, which
>defines the luns that we like to map. Do the necessary check if any of
>them is in use, and then proceed if all is available?

has already been implemented in this patch.
Hope not misunderstand your suggestion.