Messages in this thread |  | | From | Itai Nahshon <> | Subject | Re: faster boots? | Date | Mon, 8 Apr 2002 03:48:42 +0300 |
| |
On Sunday 07 April 2002 17:42 pm, Pavel Machek wrote: > Hi! > > > I'm curios, how much work can you accomplish on your laptop > > without any disk access (but you still need to save files - keeping > > them in buffers until it's time to actually write them). > > Debugging session (emacs/gcc/gdb) for half an hour with disks stopped is > easy to accomplish. > Pavel
My suggestion was: there should _never_ be dirty blocks for disks that are not spinning. Flush all dirty buffers before spinning down, and spin-up on any operation that writes to the disk (and block that operation).
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.
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.
I don't see how any of these will stop you from doing emacs/gcc/gdb with the disk stopped, as long as you are not trying to write to the disk or read from files that are not cached.
-- Itai - 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/
|  |