From: Dumitru Ciobarcianu <Dumitru.Ciobarcianu@iNES.RO>
To: Bart Samwel <bart@samwel.tk>
Cc: Kai Krueger <kai.a.krueger@web.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Laptop-mode v7 for linux 2.6.1
Date: Mon, 12 Jan 2004 22:51:09 +0200 [thread overview]
Message-ID: <1073940669.30991.7.camel@LNX.iNES.RO> (raw)
In-Reply-To: <4002F627.8000508@samwel.tk>
On Mon, 2004-01-12 at 21:31, Bart Samwel wrote:
> Kai Krueger wrote:
> > 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?
>
> Can you take a look at the message that Dumitru Ciobarcianu just sent to
> the list (about syslog), and check if it's that?
Won't help him if kdeinit is doing fsync() on every friggind write.
syslog has an option to disable that, that's all.
That's what evolution was doing until some friends helped me build an
fsync "NOP" wrapper .
This e-mail is written using "LD_PRELOAD=no-fsync.so evolution", and the
disc does not spin up every time I switch to another folder or just
another e-mail.
(Yeah, I know it's not an good ideea if I care about my e-mail, but I
keep backups... :)
Now I wonder what will happen if I do this system-wide...
hmmm... candy...
--
Cioby - "kids, don't try this at home"
next prev parent reply other threads:[~2004-01-12 20:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 17:07 [PATCH] Laptop-mode v7 for linux 2.6.1 Kai Krueger
2004-01-12 19:31 ` Bart Samwel
2004-01-12 20:51 ` Dumitru Ciobarcianu [this message]
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=1073940669.30991.7.camel@LNX.iNES.RO \
--to=dumitru.ciobarcianu@ines.ro \
--cc=bart@samwel.tk \
--cc=kai.a.krueger@web.de \
--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).