All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Jens Axboe <axboe@suse.de>
Cc: Xavier Bestel <xavier.bestel@free.fr>,
	Andreas Dilger <adilger@clusterfs.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [rfc] "laptop mode"
Date: Wed, 05 Jun 2002 12:28:04 -0700	[thread overview]
Message-ID: <3CFE6644.E70ADB5A@zip.com.au> (raw)
In-Reply-To: <3CFD453A.B6A43522@zip.com.au> <20020604233124.GA18668@turbolinux.com> <3CFD50B9.259366F4@zip.com.au> <1023272806.15438.106.camel@bip> <20020605103351.GA15883@suse.de> <3CFDEE17.FD1306A0@zip.com.au> <20020605105346.GC15883@suse.de>

Jens Axboe wrote:
> 
> ...
> > Yes, it could be per-queue.  That would add complexity to
> > the already-murky fs/fs-writeback.c.  It that justifiable?
> 
> I dunno, it's up to you. I guess this is mainly IDE specific anyways,
> but you apply the same logic to just one (for instance) of your disks on
> a home desktop system.

Well it's a convenience thing.  Not really worth a lot of code.
I expect most of the proposed functionality could be provided
from userspace anyway via the disk IO number in /proc/stat:

	old_counts=get_counters()
	while 1 {
		sleep 5
		if (old_counts != get_counters()) {
			sync
			sleep 10
			old_counts = get_counters()
		}
	}

This doesn't have the "if we flushed for any reason, reset the
timer" optimisation.  But it will work in 2.4.

So I think I'll just settle for making the ext3 journal timer
expiries tunable.

-

  parent reply	other threads:[~2002-06-05 19:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 22:54 [rfc] "laptop mode" Andrew Morton
2002-06-02  5:46 ` Pavel Machek
2002-06-04 23:13 ` Andrew Morton
2002-06-02  5:47   ` Pavel Machek
2002-06-04 23:31 ` Andreas Dilger
2002-06-04 23:43   ` Andrew Morton
2002-06-02  5:52     ` Pavel Machek
2002-06-05 10:26     ` Xavier Bestel
2002-06-05 10:33       ` Jens Axboe
2002-06-05 10:55         ` Andrew Morton
2002-06-05 10:53           ` Jens Axboe
2002-06-02  6:43             ` Pavel Machek
2002-06-05 19:28             ` Andrew Morton [this message]
2002-06-02  6:41               ` Pavel Machek
2002-06-06 18:40           ` Oliver Xymoron
2002-06-05 10:39       ` Andrew Morton
2002-06-02  5:55         ` Pavel Machek
2002-06-05 10:47         ` Xavier Bestel
2002-06-05 18:37         ` Jeff Garzik
2002-06-05 22:32           ` Padraig Brady
2002-06-05 22:39             ` Cort Dougan
2002-06-05 11:41   ` Hans-Christian Armingeon
2002-06-05 10:02     ` Thomas 'Dent' Mirlacher
2002-06-05 11:05       ` Matti Aarnio
2002-06-05 11:10     ` Ingo Oeser
2002-06-05  3:41 ` Albert D. Cahalan
2002-06-05 17:07   ` Andrew Pimlott
2002-06-05 18:04     ` Frank v Waveren
2002-06-05 18:06       ` Frank v Waveren
2002-06-05 18:14     ` Daniel Jacobowitz
2002-06-05  9:44 ` Martin Dalecki

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=3CFE6644.E70ADB5A@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=adilger@clusterfs.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xavier.bestel@free.fr \
    /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.