peloy.-
Johnny Tevessen <j.tevessen@gmx.net> wrote:
> Hi!
>
> I've got four IDE drives (hda..hdd). They're told to go to sleep
> after a while. But when some application needs to use a file on one
> of them, both the application itself and parts of the system (other
> tasks) get frozen for some seconds if the given drive needs to spin
> up first.
>
> I think this wait period should only affect the kernel fs thread
> that tries to read from the hd, but not the applications?
>
> For example, on my 64MB box (w/o X running), an application
> trying to write some few MBs to an IDE drive that's "sleeping"
> will have to wait for a few seconds, although there's enough
> memory that the fs cache could use to store the data to be written
> in while the drive spins up. This doesn't happen here; the app
> is held for seconds (in which it could calculate/parse more
> data, but it can't, since it's held in a write() call).
>
> Ideas?
>
> This is 2.1.129 speaking.
>
> 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/
>
----Eloy A. Paris Information Technology Department Rockwell Automation Venezuela Telephone: +58-2-9432311 Fax: +58-2-9431645
- 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/