[lkml]   [2000]   [Dec]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: innd mmap bug in 2.4.0-test12

On Thu, 28 Dec 2000, Chris Wedgwood wrote:

> (cc' list trimmed)
> I use ramfs for /tmp on my laptop -- it's very handy because it
> extends the amount of the the disk had spent spun down and therefore
> battery life; but writing large files into /tmp can blow away the
> system or at the very least eat away at otherwise usable ram. Not
> terribly desirable.


does anyone other than me think that the pm code is *way* too agressive about
spinning down the hard drive? my 256mb laptop (2.2.16) will only spin down the
disk for about 30 seconds before it decides it's got something else it feels
like writing out, and spins back up. Spinnup has got to be more wasteful than
just leaving the drive spinning...

unless the vfs code is cleaning dirty pages to disk when there's no activity,
then any time the vfs writes to disk, it's got something that's really hot and
shouldn't stay in ram ... if that's the case, and the frequency of such
occurrences is so high, perhaps the pm code should wait a couple of times as
long as it does before it spins down. basically, if there's still code doing
stuff, the drive should be spinning. only spindown when we're sure the user has
walked away for good :)


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 12:52    [W:0.432 / U:0.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site