linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kiko Piris <kernel@pirispons.net>
To: Jan De Luyck <lkml@kcore.org>
Cc: Bart Samwel <bart@samwel.tk>,
	linux-kernel@vger.kernel.org, Dax Kelson <dax@gurulabs.com>,
	Bartek Kania <mrbk@gnarf.org>,
	Simon Mackinlay <smackinlay@mail.com>
Subject: Re: [PATCH] Laptop-mode v7 for linux 2.6.1
Date: Mon, 12 Jan 2004 13:19:56 +0100	[thread overview]
Message-ID: <20040112121956.GA8226@portsdebalears.com> (raw)
In-Reply-To: <200401121212.44902.lkml@kcore.org>

On 12/01/2004 at 12:12, Jan De Luyck wrote:

> Patch applied, kernel built, laptop_mode activated, but my disk just doesn't 
> want to spin down... 
[...]
> But the disk never spins down. Not that I can tell, hdparm -C /dev/hda always 
> tells me active/idle, and the sdsl tool also reports 100% disk spinning...
> 
> anything else I have to activate/check?

As you don't say if you have checked it, here goes my suggestion:

First of all, you should assure there's no process doing reads [*] that
cause a cache miss (eg. daemons like postfix that check the queue every
few seconds). You can tell this running vmstat 1 and see that bi and bo
[**] stay at 0.

For example, I've observed that fetchmail (using imaps protocol, with
exim as mta) triggers a disk read that spins up the disk _always_
(regardless of what's in the cache). However, I must confess I have'nt
tracked it down (or even looked at any source code).

[*] Processes making disk writes are supposed to be "harmless", because
laptop-mode will delay those writes to disk (that's what it's supposed
to do! ;).

[**] And that's why vmstat's bo is supposed to stay at 0.

-- 
Kiko

  parent reply	other threads:[~2004-01-12 12:19 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-10 10:38 [PATCH] Laptop-mode v7 for linux 2.6.1 Bart Samwel
2004-01-10 11:15 ` Dax Kelson
2004-01-12  9:45 ` Jan De Luyck
2004-01-12  9:59   ` Bart Samwel
2004-01-12 12:50     ` Dax Kelson
2004-01-12 12:59       ` Bart Samwel
2004-01-12 15:04       ` Valdis.Kletnieks
2004-01-12 11:12 ` Jan De Luyck
2004-01-12 11:22   ` Bart Samwel
2004-01-12 12:43     ` Jan De Luyck
2004-01-12 13:41       ` Bart Samwel
2004-01-12 13:32         ` Hugang
2004-01-12 17:30         ` Dumitru Ciobarcianu
2004-01-12 12:19   ` Kiko Piris [this message]
2004-01-12 12:45     ` Jan De Luyck
2004-01-12 13:09     ` Jan De Luyck
2004-01-12 14:02       ` Jens Axboe
2004-01-13 11:00         ` Jan De Luyck
2004-01-13 11:01           ` Jens Axboe
2004-01-13 12:46             ` Bart Samwel
2004-01-13 14:21               ` Hugang
2004-01-13 17:17                 ` Jan De Luyck
2004-02-11  6:24             ` Jan De Luyck
2004-02-11 13:00               ` Micha Feigin
2004-01-12 17:07 Kai Krueger
2004-01-12 19:31 ` Bart Samwel
2004-01-12 20:51   ` Dumitru Ciobarcianu
2004-01-12 21:50     ` Bart Samwel
2004-01-12 22:51     ` Andrew Morton
2004-01-13  1:10 Kai Krueger
2004-01-13 11:58 ` Bart Samwel

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=20040112121956.GA8226@portsdebalears.com \
    --to=kernel@pirispons.net \
    --cc=bart@samwel.tk \
    --cc=dax@gurulabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@kcore.org \
    --cc=mrbk@gnarf.org \
    --cc=smackinlay@mail.com \
    /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;
as well as URLs for NNTP newsgroup(s).