ext3 never blocks interrupts. It _may_ cause increased interrupt
latency than ext2 by the very large linear writes which it does. These
may cause other parts of the kernel to block interrupts for longer.
However, more likely that it's a scheduling latency problem. Sigh.
I spent *ages* on the ext3 buffer writeout code and it's still not
ideal. Can you test with this patch applied?
It should go into 2.4.17 OK.
> By any chance, is some global lock held during any IO intensive part of
Yes, a couple. But on uniprocessor it's more a matter of the kernel
failing to context switch promptly.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/