[PATCH 1/5 v2] blk-mq: Add prep/unprep support
Matias Bjorling
m at bjorling.me
Sun Apr 19 11:12:58 PDT 2015
> On Sat, Apr 18, 2015 at 08:45:19AM +0200, Matias Bjorling wrote:
<snip>
>> The reason it shouldn't be under the a single block device, is that a target
>> should be able to provide a global address space.
>> That allows the address
>> space to grow/shrink dynamically with the disks. Allowing a continuously
>> growing address space, where disks can be added/removed as requirements grow
>> or flash ages. Not on a sector level, but on a flash block level.
>
> I don't understand what you mean with a single block device here, but I
> suspect we're talking past each other somehow.
Sorry. I meant that several block devices should form a single address
space (exposed as a single block device), consisting of all the flash
blocks. Applications could then get/put from that.
Thanks for your feedback. I'll push the pieces around and make the
integration self-contained outside of the block layer.
More information about the Linux-nvme
mailing list