[lkml]   [1998]   [Nov]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectIDE freeze for seconds

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).


This is 2.1.129 speaking.

Trust no-one.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:45    [W:0.070 / U:2.192 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site