![]() | |||||||||||||
Messages in this thread |
> > and spin-up on any operation that writes to the disk (and block that > > operation). > > Absolutely not! I don't want my writes to spin up the drive. Even if you sync ? > > The opposite to that (which I do not like) processes create as many > > dirty buffers as they want and disk spins up only on sync() or when > > the system is starving for usable memory. > > Maybe you don't like that, but many of us with laptops prefer that > behaviour. And for many reasons, it is definately the correct > behaviour. You are definitely right. I'd even wish for swapping out stuff and doing a drastic read ahead before spinning down. > > An aletrnate ides (more drastic) is that fle systems can mount > > internally read-only when a disk is spinned-down. Means - you cannot > > spin down when there is a file handle open for writing. Other than > > this there are advantages. > > Undesirable behaviour. Absolutely. One disk is typical and log files will be open. Regards Oliver - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:25 [from the cache] ©2003-2008 | |||||||||||||