| 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
| ||
|
Message-ID: <5533F02A.6020208@bjorling.me> Date: Sun, 19 Apr 2015 20:12:58 +0200 From: Matias Bjorling <m@...rling.me> To: Christoph Hellwig <hch@...radead.org> CC: keith.busch@...el.com, javier@...etta.io, linux-kernel@...r.kernel.org, linux-nvme@...ts.infradead.org, axboe@...com, linux-fsdevel@...r.kernel.org Subject: Re: [PATCH 1/5 v2] blk-mq: Add prep/unprep support > 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists