From: Pavel Machek <pavel@suse.cz>
To: Erik Hensema <erik@hensema.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Delaying writes to disk when there's no need
Date: Sat, 29 Mar 2003 00:12:48 +0100 [thread overview]
Message-ID: <20030328231248.GH5147@zaurus.ucw.cz> (raw)
In-Reply-To: <slrnb843gi.2tt.usenet@bender.home.hensema.net>
Hi!
> In all kernels I've tested writes to disk are delayed a long time even when
> there's no need to do so.
>
> A very simple test shows this: on an otherwise idle system, create a tar of
> a NFS-mounted filesystem to a local disk. The kernel starts writing out the
> data after 30 seconds, while a slow and steady stream would be much nicer
> to the system, I think.
>
Well, doing writeback sooner when disks
are idle might be good idea; detecting
if disk is idle might not be too easy, through.
OTOH, raid resync already has some
such detection?
Pavel
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
next prev parent reply other threads:[~2003-03-30 19:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 20:31 Delaying writes to disk when there's no need Erik Hensema
2003-03-27 9:06 ` Helge Hafting
2003-03-27 11:22 ` Erik Hensema
2003-03-28 23:12 ` Pavel Machek [this message]
2003-03-31 12:00 ` Erik Hensema
2003-03-31 13:42 ` Helge Hafting
2003-03-31 14:45 ` Oliver Neukum
2003-03-31 22:02 ` Nick Piggin
2003-03-31 22:22 ` Chris Friesen
2003-03-31 22:35 ` Nick Piggin
2003-03-31 22:51 ` John Bradford
2003-03-31 22:58 ` Nick Piggin
2003-03-31 22:45 ` Andrew Morton
2003-03-31 23:03 ` Nick Piggin
2003-03-31 23:32 ` Ingo Oeser
2003-04-01 0:02 ` Andrew Morton
2003-04-01 0:43 ` Daniel Pittman
2003-04-01 1:09 ` Andrew Morton
2003-04-01 1:34 ` Daniel Pittman
2003-04-01 1:45 ` Andrew Morton
[not found] ` <3E88EB3D.6020409@cyberone.com.au>
2003-04-01 1:39 ` Andrew Morton
[not found] <20030326204012$188c@gated-at.bofh.it>
[not found] ` <20030327091007$22a5@gated-at.bofh.it>
[not found] ` <20030327113014$37b4@gated-at.bofh.it>
2003-03-28 10:18 ` Tim Connors
2003-03-30 17:38 ` Helge Hafting
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=20030328231248.GH5147@zaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=erik@hensema.net \
--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 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.