> 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.
Would it be possible to change this? Even on UP there's no reason
why the application has to wait for the drive if it's just
writing a file. I assume that on SMP only one of the cpus/processes
would have to wait?
I don't know too much about SMP systems, so please forgive if I
said something too stupid. :-)
> Other IDE interfaces are free to continue working in parallel.
Yes, they do. But on IDE-only systems this is more than annoying.
Would it be hard to implement a thread/task/process that writes
back data to disk? I guess this would be the logical consequence.
ciao,
johnny
-- Trust no-one.- 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/