public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Mike Galbraith <mikeg@wen-online.de>,
	Rik van Riel <riel@conectiva.com.br>,
	Pavel Machek <pavel@suse.cz>, John Stoffel <stoffel@casc.com>,
	Roger Larsson <roger.larsson@norran.net>, <thunder7@xs4all.nl>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Early flush (was: spindown)
Date: Wed, 20 Jun 2001 10:12:38 -0600	[thread overview]
Message-ID: <200106201612.f5KGCca06372@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <01062016294903.00439@starship>
In-Reply-To: <Pine.LNX.4.33.0106171156410.318-100000@mikeg.weiden.de> <01062003503300.00439@starship> <200106200439.f5K4d4501462@vindaloo.ras.ucalgary.ca> <01062016294903.00439@starship>

Daniel Phillips writes:
> On Wednesday 20 June 2001 06:39, Richard Gooch wrote:
> > Starting I/O immediately if there is no load sounds nice. However,
> > what about the other case, when the disc is already spun down (and
> > hence there's no I/O load either)? I want the system to avoid doing
> > writes while the disc is spun down. I'm quite happy for the system to
> > accumulate dirtied pages/buffers, reclaiming clean pages as needed,
> > until it absolutely has to start writing out (or I call sync(2)).
> 
> I'd like that too, but what about sync writes?  As things stand now,
> there is no option but to spin the disk back up.  To get around this
> we'd have to change the basic behavior of the block device and
> that's doable, but it's an entirely different proposition than the
> little patch above.

I don't care as much about sync writes. They don't seem to happen very
often on my boxes.

> You know about this project no doubt:
> 
>    http://noflushd.sourceforge.net/

Only vaguely. It's huge. Over 2300 lines of C code and >560 lines in
.h files! As you say, not really lightweight. There must be a better
way. Also, I suspect (without having looked at the code) that it
doesn't handle memory pressure well. Things may get nasty when we run
low on free pages.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  reply	other threads:[~2001-06-20 16:13 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13 19:31 2.4.6-pre2, pre3 VM Behavior Tom Sightler
2001-06-13 20:21 ` Rik van Riel
2001-06-14  1:49   ` Tom Sightler
2001-06-14  3:16     ` Rik van Riel
2001-06-14  7:59       ` Laramie Leavitt
2001-06-14  9:24         ` Helge Hafting
2001-06-14 17:38           ` Mark Hahn
2001-06-15  8:27             ` Helge Hafting
2001-06-14  8:47       ` Daniel Phillips
2001-06-14 15:10         ` John Stoffel
2001-06-14 18:25           ` Daniel Phillips
2001-06-14 20:23         ` Roger Larsson
2001-06-14 20:39           ` John Stoffel
2001-06-14 20:51             ` Rik van Riel
2001-06-14 21:33               ` John Stoffel
2001-06-14 22:23                 ` Rik van Riel
2001-06-15 15:23             ` spindown [was Re: 2.4.6-pre2, pre3 VM Behavior] Pavel Machek
2001-06-16 20:50               ` Daniel Phillips
2001-06-16 21:06                 ` Rik van Riel
2001-06-16 21:25                   ` Rik van Riel
2001-06-16 21:44                   ` Daniel Phillips
2001-06-16 21:54                     ` Rik van Riel
2001-06-17 10:28                       ` Daniel Phillips
2001-06-17 10:05                     ` Mike Galbraith
2001-06-17 12:49                       ` (lkml)Re: " thunder7
2001-06-17 16:40                         ` Mike Galbraith
2001-06-18 14:22                       ` Daniel Phillips
2001-06-19  4:35                         ` Mike Galbraith
2001-06-20  1:50                         ` [RFC] Early flush (was: spindown) Daniel Phillips
2001-06-20  4:39                           ` Richard Gooch
2001-06-20 14:29                             ` Daniel Phillips
2001-06-20 16:12                               ` Richard Gooch [this message]
2001-06-22 23:25                                 ` Daniel Kobras
2001-06-23  5:10                                   ` Daniel Phillips
2001-06-25 11:33                                     ` Pavel Machek
2001-06-25 11:31                                 ` Pavel Machek
2001-06-20 20:58                           ` Tom Sightler
2001-06-20 22:09                             ` Daniel Phillips
2001-06-24  3:20                             ` Anuradha Ratnaweera
2001-06-24 11:14                               ` Daniel Phillips
2001-06-24 15:06                               ` Rik van Riel
2001-06-24 16:21                                 ` Daniel Phillips
2001-06-18 20:21               ` spindown Simon Huggins
2001-06-19 10:46                 ` spindown Pavel Machek
2001-06-20 16:52                   ` spindown Daniel Phillips
2001-06-20 17:32                     ` spindown Rik van Riel
2001-06-20 18:00                       ` spindown Daniel Phillips
2001-06-21 16:07                   ` spindown Jamie Lokier
2001-06-22 22:09                     ` spindown Daniel Kobras
2001-06-28  0:27                     ` spindown Troy Benjegerdes
2001-06-15  6:04           ` 2.4.6-pre2, pre3 VM Behavior Mike Galbraith
2001-06-14  8:30   ` Mike Galbraith

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=200106201612.f5KGCca06372@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.de \
    --cc=pavel@suse.cz \
    --cc=phillips@bonn-fries.net \
    --cc=riel@conectiva.com.br \
    --cc=roger.larsson@norran.net \
    --cc=stoffel@casc.com \
    --cc=thunder7@xs4all.nl \
    /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