That might work if the FS ran on a separate thread.
But under Linux, the "fs thread" *is* the application process.
The reason other tasks may also be held up during the spin-up
is that the disk-queue is blocked on the r/w request that
caused the spin-up, and other requests for the same MAJOR
(IDE interface) cannot proceed until it is serviced.
Other IDE interfaces are free to continue working in parallel.
-- mlord@pobox.com- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/