public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Rychter <jan@rychter.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] laptop mode
Date: Fri, 17 Oct 2003 12:42:13 -0700	[thread overview]
Message-ID: <m2ekxb7isq.fsf@tnuctip.rychter.com> (raw)
In-Reply-To: 20031009141143.GF1232@suse.de

[-- Attachment #1: Type: text/plain, Size: 2008 bytes --]

>>>>> "Jens" == Jens Axboe <axboe@suse.de> writes:
 Jens> On Thu, Oct 09 2003, Marcelo Tosatti wrote:
 >> On Thu, 9 Oct 2003, Jeff Garzik wrote:
 > Linux Kernel Mailing List wrote:
 > > ChangeSet 1.1150.1.52, 2003/10/08 10:49:45-03:00, axboe@suse.de
 > > 	[PATCH] laptop mode
 > >
 > > 	Hi Marcelo,
 > >
 > > 	Lots of people have been using this patch with great success,
 > > 	and it's been in the SuSE kernel for some months now too. It is
 > > 	also in the -benh ppc tree
 > >
 > > 	Basically, it introduces a write back mode of dirty and journal
 > > 	data that is more suitable for laptops. At the block layer end,
 > > 	it schedules write out of dirty data after the disk has been
 > > 	idle for 5 seconds.
 > >
 > > 	Laptop mode can be switched on and off with
 > > 	/proc/sys/vm/laptop_mode.  There is also a block_dump sysctl,
 > > 	which if enabled will dump who dirties and writes out data. This
 > > 	is very helpful in pinning down who is causing unnecessary
 > > 	writes to the disk.
 >
 > Red Hat just dropped this patch since it was suspected of data
 > corruption ;-(
 >>
 >> Uh, oh... Jens?

 Jens> See my previous mail. I don't see any problems with it, and I've
 Jens> certainly not heard of (or experienced myself) problems with the
 Jens> patch.  I'm waiting for Jeff to expand on his mail, surely he/RH
 Jens> must know more about this issue.

FWIW, I've been using laptop-mode for a long time now, with no problems
whatsoever. It's a great addition and really helps laptop users.

On a related note, a very desirable feature would be to be able to trace
which processes do I/O. Unfortunately, Linux distributions aren't very
well adapted to laptops and many applications are way too
"trigger-happy" when it comes to hard drive accesses. I guess most
developers don't use laptops and just assume that they can write or
read data at will. It is very difficult to trace the culprits when your
HD light goes on every couple of seconds.

--J.

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  parent reply	other threads:[~2003-10-17 19:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200310091103.h99B31ug014566@hera.kernel.org>
2003-10-09 14:02 ` [PATCH] laptop mode Jeff Garzik
2003-10-09 14:05   ` Jens Axboe
2003-10-09 14:17     ` Dave Jones
2003-10-09 14:26       ` Jens Axboe
2003-10-11 11:49         ` Pavel Machek
2003-10-11 13:59           ` Jens Axboe
2003-10-12 22:45             ` Barry K. Nathan
2003-10-14 17:50               ` Jeff Garzik
2003-10-09 14:09   ` Marcelo Tosatti
2003-10-09 14:11     ` Jens Axboe
2003-10-09 14:18       ` Jeff Garzik
2003-10-09 14:21         ` Jens Axboe
2003-10-09 14:28       ` Dave Jones
2003-10-17 19:42       ` Jan Rychter [this message]
2003-10-18 12:52         ` Jens Axboe

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=m2ekxb7isq.fsf@tnuctip.rychter.com \
    --to=jan@rychter.com \
    --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