From: "Matias Bjørling" <m@bjorling.me>
To: "Wenwei Tao" <ww.tao0320@gmail.com>, "Matias Bjørling" <mb@lightnvm.io>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] lightnvm: add non-continuous lun target creation support
Date: Thu, 21 Jan 2016 17:02:31 +0100 [thread overview]
Message-ID: <56A10117.2000002@bjorling.me> (raw)
In-Reply-To: <CACygaLDJOtYyRm+ehf-z_-tAg-S2GfBjkkE6Wp0yc+iCXacUjA@mail.gmail.com>
On 01/21/2016 02:58 PM, Wenwei Tao wrote:
> 2016-01-21 17:49 GMT+08:00 Matias Bjørling <mb@lightnvm.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.
Yeap :)
next prev parent reply other threads:[~2016-01-21 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 11:44 [RFC PATCH 1/2] lightnvm: specify target's logical address area Wenwei Tao
2016-01-15 11:44 ` [RFC PATCH 2/2] lightnvm: add non-continuous lun target creation support Wenwei Tao
2016-01-20 13:19 ` Matias Bjørling
2016-01-21 7:44 ` Wenwei Tao
2016-01-21 7:53 ` Matias Bjørling
2016-01-21 9:47 ` Wenwei Tao
2016-01-21 9:49 ` Matias Bjørling
2016-01-21 13:58 ` Wenwei Tao
2016-01-21 16:02 ` Matias Bjørling [this message]
2016-01-20 13:03 ` [RFC PATCH 1/2] lightnvm: specify target's logical address area Matias Bjørling
2016-01-21 7:05 ` Wenwei Tao
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=56A10117.2000002@bjorling.me \
--to=m@bjorling.me \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@lightnvm.io \
--cc=ww.tao0320@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.