| 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: <b1e142760611302316w5917bc67q5a9f26e1d069f716@mail.gmail.com> Date: Fri, 1 Dec 2006 02:16:15 -0500 From: "Ming Zhao" <mingzhao99th@...il.com> To: "device-mapper development" <dm-devel@...hat.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [dm-devel] [RFC][PATCH] dm-cache: block level disk cache target for device mapper On 11/30/06, Jens Wilke <jens.wilke@...ibm.com> wrote: > - You don't keep track of I/O on the fly to the cache that is mapped > directly in cache_hit(). How do you make sure that this I/O is completed > before you replace a cache block? The previous I/O from cache hit and the later I/O for cache replacement should be queued in order on the cache block device - is this a safe assumption? > - The cache block index is hashed, this means the cache data blocks are not > clustered. I don't think you can solve this problem with a proper hash function. > Perhaps you should consider a (B-)Tree structure for that. The current hash algorithm does clustering to some extent by mapping consecutive blocks from the source device to consecutive blocks on the cache device. But I agree that more sophisticated algorithms can be studied. Thanks a lot for the suggestions. I will try to incorporate them in the next patch. - Ming - 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