All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan De Luyck <lkml@kcore.org>
To: Hugang <hugang@soulinfo.com>, Bart Samwel <bart@samwel.tk>
Cc: Jens Axboe <axboe@suse.de>, Kiko Piris <kernel@pirispons.net>,
	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: Tue, 13 Jan 2004 18:17:42 +0100	[thread overview]
Message-ID: <200401131817.42341.lkml@kcore.org> (raw)
In-Reply-To: <20040113222117.21d1ac0b@localhost>

On Tuesday 13 January 2004 15:21, Hugang wrote:
> On Tue, 13 Jan 2004 13:46:54 +0100
>
> Bart Samwel <bart@samwel.tk> wrote:
> > The reiserfs patch for "commit=" was included in Linux 2.6.1. I really
> > don't know if it works with laptop mode, haven't tested it -- I don't
> > use reiserfs. So, let's ask the world: is there anyone out there who is
> > running laptop mode *successfully* with reiserfs?
>
> Yes, I'm use reiserfs in 2.6.1 with laptop_mode patch. It works fine for
> me, I use cpudyn daemon to let spin download harddisk. In cpudyn.conf I
> changed TIMEOUT from 120 to 10. When i reading email/web, the harddisk can
> spin down for very long time (>3min).
>
> So you can try cpudynd.

Well, i used the smart-spindown script posted earlier, but even when not 
touching the laptop it gets a spindown of 40 seconds max. Then something 
always has to wake it up.

> /dev/hda13 on / type ext3 (rw,noatime,errors=remount-ro,commit=600)

It is rather annoying that this commit parameter isn't documented anywhere... 
man mount doesn't know it, nor does the kernel documentation.

Jan

-- 
The executioner is, I hear, very expert, and my neck is very slender.
		-- Anne Boleyn


  reply	other threads:[~2004-01-13 17:18 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 [this message]
2004-02-11  6:24             ` Jan De Luyck
2004-02-11 13:00               ` Micha Feigin
  -- strict thread matches above, loose matches on Subject: below --
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=200401131817.42341.lkml@kcore.org \
    --to=lkml@kcore.org \
    --cc=axboe@suse.de \
    --cc=bart@samwel.tk \
    --cc=dax@gurulabs.com \
    --cc=hugang@soulinfo.com \
    --cc=kernel@pirispons.net \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.