From: Nick Piggin <piggin@cyberone.com.au>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: erik@hensema.net, linux-kernel@vger.kernel.org
Subject: Re: Delaying writes to disk when there's no need
Date: Tue, 01 Apr 2003 08:02:33 +1000 [thread overview]
Message-ID: <3E88BAF9.8040100@cyberone.com.au> (raw)
In-Reply-To: <3E8845A8.20107@aitel.hist.no>
Helge Hafting wrote:
> Erik Hensema wrote:
> [...]
>
>> Helge Hafting already pointed out that writing out the data earlier
>> isn't
>> desirable. The problem isn't in the waiting: the problem is in the
>> writing.
>> I think the current kernel tries to write too much data too fast when
>> there's absolutely no reason to do so. It should probably gently
>> write out
>> small amounts of data until there is a more pressing need for memory.
>>
> I don't think the problem is "writing a large chunk", rather that this
> chunk is scheduled for writing a bit too late. Memory is filling up
> and the process producing data us throttled while waiting for
> the write to free up pages. Then the "huge chunk" of pages is released,
> and memory is allowed to fill up for too long again.
>
> Seem to me the correct solution is to start writing out
> things long before memory gets so full that we need to
> throttle the producer.
I haven't thought about this much, but it seems to me that
doing writeout whenever the disk would otherwise be idle
(and we have dirty memory to write out) would be a good
solution.
next prev parent reply other threads:[~2003-03-31 21:54 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
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 [this message]
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=3E88BAF9.8040100@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=erik@hensema.net \
--cc=helgehaf@aitel.hist.no \
--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.