On Thu, Mar 01, 2012 at 09:49:41PM -0500, Zach Brown wrote: > > >*why* is it interesting to allow kernel code to submit aio > >requests, and loop devices to be able to direct I/O requests all the > >way to the underlying file systems. > > As I understood it, lo those years ago, the use case was virtual guests > provisioned on loopback devices on files in the host file system. > > In this use case either having loop implement a second writeback cache > or having it only capable of one sync IO in flight at a time is pretty > bad when you're trying to offer consistent and performant file systems > to the guest. I'm confused though why the guests would be pointed at the loopback device, as opposed to just simply attaching to the file directly. Or is this some kind of Xen limitation? With qemu/kvm I don't see why it would make sense to indirect through the loop device.... - Ted -- 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
