From: Micha Feigin <michf@post.tau.ac.il>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Laptop-mode v7 for linux 2.6.1
Date: Wed, 11 Feb 2004 15:00:24 +0200 [thread overview]
Message-ID: <20040211130024.GJ3854@luna.mooo.com> (raw)
In-Reply-To: <200402110724.18676.lkml@kcore.org>
On Wed, Feb 11, 2004 at 07:24:18AM +0100, Jan De Luyck wrote:
> On Tuesday 13 January 2004 12:01, Jens Axboe wrote:
> > On Tue, Jan 13 2004, Jan De Luyck wrote:
> > > On Monday 12 January 2004 15:02, Jens Axboe wrote:
> > > > bo is accounted when io is actually put on the pending queue for the
> > > > disk, so they really do go hand in hand. So you should use block_dump
> > > > to find out why.
> > >
> > > It's nearly always reiserfs that causes the disk to spin up. Also, I'm
> > > seeting the harddisk led light up every 5-7 seconds :-( weird.
> >
> > Does 2.6 laptop mode patch even include the necessary reiser changes to
> > make this work properly?
>
> To followup on this: I've recently moved my entire installation to ext3 (I had
> to RMA the disk, tarred everything up, formatted another disk, put everything
> back but on ext3 this time), on which the laptopmode actually makes a
> difference. I can hear the disk spindown, and it stays that way for a
> reasonably long time (e.g. +- 10 minutes has happened).
>
> So there does seem to be a serious difference between the reiserfs commit
> option and the ext3 option.
>
The reiserfs commit option doesn't work to suppress reiserfs journal
writing to disk. The value that needs to be changes is the transaction
max age instead of the commit max age which is being change now.
This is under work along with adding xfs support and fixing the ext3
commit option (there is no reset to default commit value option at the
moment).
It won't take too long but if anyone is impatient I can send them a
patch to fix reiserfs.
> Just letting you folks know.
>
> Jan
>
> --
> Baruch's Observation:
> If all you have is a hammer, everything looks like a nail.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2004-02-11 13:00 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
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 [this message]
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=20040211130024.GJ3854@luna.mooo.com \
--to=michf@post.tau.ac.il \
--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).