On Friday 01 December 2006 08:16, Ming Zhao wrote: > On 11/30/06, Jens Wilke <jens.wilke@xxxxxxxxxx> 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? I don't think you can assume that the request processing in the host is ordered without sychronization. Everything you queue in your worker thread is serialized by that. Everything else is out of your control and each thread may be scheduled or not. Maybe we have certain guarantees through DM or the block I/O layer, that I don't know. Can somebody else step in here? Best, Jens -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
