Hello, On 07/27/2010 08:35 PM, Vivek Goyal wrote: > IIUC, what Christoph is trying to address is that if write cache is > not enabled then we don't need flushing semantics. We can get rid of > need of request ordering semantics by waiting on dependent request to > finish instead of issuing a barrier. That way we will not issue barriers > no request queue drains and that possibly will help with throughput. What I don't get here is if filesystems order requests already by waiting for completions why do they use barriers at all? All they need is flush request after all the preceding requests are known to be complete. Having writeback cache or not doesn't make any difference w.r.t. request ordering requirements. If filesystems don't need the heavy handed ordering provided by barrier, it should just use flush instead of barrier. If filesystem needs the barrier ordering, whether the device in question is battery backed and costs more than a house doesn't make any difference. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
