From: "Kai Krueger" <kai.a.krueger@web.de>
To: "BartSamwel" <bart@samwel.tk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Laptop-mode v7 for linux 2.6.1
Date: Mon, 12 Jan 2004 18:07:44 +0100 [thread overview]
Message-ID: <200401121707.i0CH7iQ11796@mailgate5.cinetic.de> (raw)
Bart Samwel <bart@samwel.tk> schrieb am 12.01.04 14:47:20:
>
> Jan De Luyck wrote:
> >>2. Stop klogd, do "echo 1 > /proc/sys/vm/block_dump" and see which
> >>process keeps your disk spun up using dmesg.
> >
> > Welll.... i see no READs, and the writes i see is spamd, kmail, pdflush,
> > reiserfs/0.
>
> How are the WRITEs grouped, are they grouped together or do they seem to
> occur more evenly spaced? When you use "sync", how long until the next
> WRITE? What are the values of /proc/sys/vm/dirty_expire_centisecs and
> /proc/sys/vm/dirty_writeback_centisecs? Are you sure you are running a
> kernel that supports the commit= option with reiserfs? (This option was
> added in 2.6.1.)
>
> I've never tested laptop mode with reiserfs BTW, does anybody else here
> have experience with laptop mode and reiserfs?
I'm currently trying kernel 2.6.1-mm1 with laptop-mode on a reiserfs partition.
If I kill all daemons running on the system and do nothing with it, I can achieve the 10 minutes spin down time I had expected from laptop-mode. However as soon as I start up X with KDE I get regular spin ups every 30 seconds. Looking at the output of "echo 1 > /proc/sys/vm/block_dump", I see an entry every 30 seconds of "kdeinit(15145): WRITE block 65680 on hda1" followed by a whole load of "reiserfs/0(12): dirtied page" and "reisers/0(12): WRITE block XXXXX on hda1".
Due to the regular 30 second interval writes of kdeinit: kded to block 65680, laptop-mode is not particularly usable on this system.
Is this a problem with reiserfs or with kde and is there any fix available?
>
> -- Bart
Kai
______________________________________________________________________________
Erdbeben im Iran: Zehntausende Kinder brauchen Hilfe. UNICEF hilft den
Kindern - helfen Sie mit! https://www.unicef.de/spe/spe_03.php
next reply other threads:[~2004-01-12 17:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 17:07 Kai Krueger [this message]
2004-01-12 19:31 ` [PATCH] Laptop-mode v7 for linux 2.6.1 Bart Samwel
2004-01-12 20:51 ` Dumitru Ciobarcianu
2004-01-12 21:50 ` Bart Samwel
2004-01-12 22:51 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-01-13 1:10 Kai Krueger
2004-01-13 11:58 ` Bart Samwel
2004-01-10 10:38 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
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
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=200401121707.i0CH7iQ11796@mailgate5.cinetic.de \
--to=kai.a.krueger@web.de \
--cc=bart@samwel.tk \
--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;
as well as URLs for NNTP newsgroup(s).