On 2011-09-01 14:14, Werner Fischer wrote: >> 3) the fusion IO device driver can hook itself in where you put it, or >> also up above the I/O scheduler (based on a module load option). > Oh wow, that sounds interesting. Does this mean that in this case (IO > device driver above the I/O scheduler) simply no I/O scheduler is used? It'll hook in similarly to where stacked devices like md/dm do. So yes, it's bypassing the IO scheduler. One note on that - this mode is going away in the future. You end up losing out on request merging, so write performance is hampered, for one. The Micron pci-e mtip32xx driver does similarly, as does the nvmhci-express driver from Intel. IMHO it's largely due to inefficiencies in the IO stack, once we get those fixed, we should be getting back to the one true single IO mode for a driver. I consider the bypass setup a bit of a hack and work-around. -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
