From: Daniel Phillips <phillips@bonn-fries.net>
To: Rik van Riel <riel@conectiva.com.br>,
Linus Torvalds <torvalds@transmeta.com>
Cc: Chris Mason <mason@suse.com>, linux-mm@kvack.org
Subject: Re: [PATCH] kill flush_dirty_buffers
Date: Mon, 6 Aug 2001 21:53:34 +0200 [thread overview]
Message-ID: <0108062153340J.00294@starship> (raw)
In-Reply-To: <Pine.LNX.4.33L.0108061538360.1439-100000@duckman.distro.conectiva>
On Monday 06 August 2001 20:39, Rik van Riel wrote:
> On Mon, 6 Aug 2001, Linus Torvalds wrote:
> > The other issue is that I suspect that "flushtime" is completely
> > useless these days, and should just be dropped. If we've decided to
> > start flushing stuff out, we shouldn't stop flushing just because
> > some buffer hasn't quite reached the proper age yet.
It's still useful for making sure dirty buffers don't get too old.
> > We'd have been
> > better off maybe deciding not to even _start_ flushing at all, but
> > once we've started, we might as well do the dirty buffers we see (up
> > to a maximum that is due to IO _latency_, not due to "how long since
> > this buffer was dirtied")
*nod*
Where IO latency isn't that well defined at the moment. Consider a a
slow and a fast writable block device on the same system. The ideal
length of the IO queue depends on which has most of the IO activity.
This suggests that buffer flushing needs to be per-device.
--
Daniel
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2001-08-06 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-06 17:09 Chris Mason
2001-08-06 18:00 ` Linus Torvalds
2001-08-06 18:39 ` Rik van Riel
2001-08-06 19:53 ` Daniel Phillips [this message]
2001-08-07 21:19 ` Jens Axboe
2001-08-06 21:14 ` Chris Mason
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=0108062153340J.00294@starship \
--to=phillips@bonn-fries.net \
--cc=linux-mm@kvack.org \
--cc=mason@suse.com \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.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