mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Andrew Morton <akpm@zip.com.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [rfc] "laptop mode"
Date: Sun, 2 Jun 2002 05:46:22 +0000	[thread overview]
Message-ID: <20020602054621.E121@toy.ucw.cz> (raw)
In-Reply-To: <3CFD453A.B6A43522@zip.com.au>

Hi!

> laptop_mode
> -----------
> 
> Setting this entry to '1' will put the kernel's dirty data writeout
> algorithms into a mode which is better suited to laptop/notebook
> computers.  This mode is specifically designed to minimise the
> frequency of disk spinups.  Laptop mode works as follows:
> 
> - Dirty data remains in memory for longer periods of time (controlled
>   by laptop_writeback_centisecs).
> 
> - If there is pending dirty data and the disk is spun up for any
>   reason (even for a read) then all dirty data will be written back
>   shortly afterwards.  ie: when the disk is spun up, make good use of
>   it.
> 
> - When the decision is made to write back some dirty data, the kernel
>   will write back all dirty data.

Nice!

> laptop_writeback_centisecs
> --------------------------
> 
> This tunable determines the maximum age of dirty data when the machine
> is operating in Laptop mode.  The default value is 30000 - five

Well, I run my notebooks in similar mode with writeback set essentialy to
infinity. I do it even on my home server....

> This implementation doesn't try to be very smart - there's a direct
> call out of do_ide_request() into the writeback code.  This couldn't
> be done from within ll_rw_blk.c because then a write to the ramdisk
> would spin the disk up.   Even as-is, a read from the IDE CDROM
> drive will cause the IDE hard disk to spin up and flush data, so

It would  nice to do this per disk.... If you have server with one active
and one inactive disk, you want the inactive one to sleep.
								Pavel
-- 
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.


  reply	other threads:[~2002-06-06 18:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 22:54 Andrew Morton
2002-06-02  5:46 ` Pavel Machek [this message]
2002-06-04 23:13 ` Andrew Morton
2002-06-02  5:47   ` Pavel Machek
2002-06-04 23:31 ` Andreas Dilger
2002-06-04 23:43   ` Andrew Morton
2002-06-02  5:52     ` Pavel Machek
2002-06-05 10:26     ` Xavier Bestel
2002-06-05 10:33       ` Jens Axboe
2002-06-05 10:55         ` Andrew Morton
2002-06-05 10:53           ` Jens Axboe
2002-06-02  6:43             ` Pavel Machek
2002-06-05 19:28             ` Andrew Morton
2002-06-02  6:41               ` Pavel Machek
2002-06-06 18:40           ` Oliver Xymoron
2002-06-05 10:39       ` Andrew Morton
2002-06-02  5:55         ` Pavel Machek
2002-06-05 10:47         ` Xavier Bestel
2002-06-05 18:37         ` Jeff Garzik
2002-06-05 22:32           ` Padraig Brady
2002-06-05 22:39             ` Cort Dougan
2002-06-05 11:41   ` Hans-Christian Armingeon
2002-06-05 10:02     ` Thomas 'Dent' Mirlacher
2002-06-05 11:05       ` Matti Aarnio
2002-06-05 11:10     ` Ingo Oeser
2002-06-05  3:41 ` Albert D. Cahalan
2002-06-05 17:07   ` Andrew Pimlott
2002-06-05 18:04     ` Frank v Waveren
2002-06-05 18:06       ` Frank v Waveren
2002-06-05 18:14     ` Daniel Jacobowitz
2002-06-05  9:44 ` Martin Dalecki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020602054621.E121@toy.ucw.cz \
    --to=pavel@suse.cz \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®