On Thu, 2008-07-31 at 09:46 -0400, Ric Wheeler wrote: > Not sure if this is just an 8-way, multithreaded test, but my run of the > latest unstable tree ground to a halt with lock messages (see the > attached, compressed log for details ;-)) On the good news side, it did > run for around 8 hours before the first message was logged. I just merged Yan's missing hunks that might help explain this. At least for fs_mark, you shouldn't really be hitting the throttling code very often. But, until I fully thread the allocator I can't completely get rid of the stalls. That's one of the first things on my list for after v0.16 One of your procs is stuck in generic_unplug_device, and that one didn't come from me ;) Sounds like the IO subsystem might be taking short breaks as well. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
