On Thu, Jul 29, 2010 at 11:17:21PM -0400, Vivek Goyal wrote: > To me it looked like as if everything is there and it is just a matter > of skipping elevator draining and request queue draining. The problem is that is just appears to be so. The code blocking only the next barrier for tagged writes is there, but in that form it doesn't work and probably never did. When I try to use it and debug it I always get my post-flush request issued before the barrier request has finished. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
