From: Jens Axboe <axboe@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
davej@redhat.com, arjanv@redhat.com
Subject: Re: [PATCH] laptop mode
Date: Thu, 9 Oct 2003 16:21:48 +0200 [thread overview]
Message-ID: <20031009142148.GH1232@suse.de> (raw)
In-Reply-To: <3F856E27.1010203@pobox.com>
On Thu, Oct 09 2003, Jeff Garzik wrote:
> Jens Axboe wrote:
> >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?
> >
> >
> >See my previous mail. I don't see any problems with it, and I've
> >certainly not heard of (or experienced myself) problems with the patch.
> >I'm waiting for Jeff to expand on his mail, surely he/RH must know more
> >about this issue.
>
>
> That's 100% of my knowledge. Talk to arjan/davej/sct for more info...
CC'ed
> That's what RH's field testing showed us, ignore it if you wish... :)
As far as I can tell, laptop-mode cannot cause any corruption on it own
that cannot otherwise happen without laptop mode. So if you see
corruption, it is most likely exposing some other bug. Or the field
users run out of battery and 10 minutes of work goes down the drain,
that's a calcuated risk though.
--
Jens Axboe
next prev parent reply other threads:[~2003-10-09 14:22 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 [this message]
2003-10-09 14:28 ` Dave Jones
2003-10-17 19:42 ` Jan Rychter
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=20031009142148.GH1232@suse.de \
--to=axboe@suse.de \
--cc=arjanv@redhat.com \
--cc=davej@redhat.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox