On Tue, May 29 2007, Zach Brown wrote: Thanks for picking this up, Zach!
> - cfq gets confused, share io_context amongst threads? Yeah, it'll confuse CFQ a lot actually. The threads either need to share an io context (clean approach, however will introduce locking for things that were previously lockless), or CFQ needs to get better support for cooperating processes. The problem is that CFQ will wait for a dependent IO for a given process, which may arrive from a totally unrelated process. For the fio testing, we can make some improvements there. Right now you don't get any concurrency of the io requests if you set eg iodepth=32, as the 32 requests will be submitted as a linked chain of atoms. For io saturation, that's not really what you want. I'll take a stab at improving both of the above. -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
