From: <pcg@goof.com ( Marc) (A.) (Lehmann )>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Significant performace improvements on reiserfs systems, kupdated bugfixes
Date: Fri, 21 Sep 2001 22:12:25 +0200 [thread overview]
Message-ID: <20010921221225.A22402@schmorp.de> (raw)
In-Reply-To: <20010920101544.A14526@turbolinux.com> <Pine.LNX.4.30.0109210015190.19847-100000@gamma.student.ljbc>
In-Reply-To: <Pine.LNX.4.30.0109210015190.19847-100000@gamma.student.ljbc>
On Fri, Sep 21, 2001 at 12:22:59AM +0800, Beau Kuiper <kuib-kl@ljbc.wa.edu.au> wrote:
> Also, it is nicer behaviour not to write out to disk before the time
> indicated in the bdflush tuning structure. It allows sys admins to better
> tune the overal performace of a system. (unless the kernel need s more
> free memory)
A contiguous write doesn't cost anything much, so it could be major
win if the kernel could flush dirty buffers that are behind and after
the dirty block to be written. But this would nicely conflict with
allocate-on-flush ;)
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@goof.com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
next prev parent reply other threads:[~2001-09-21 20:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 7:12 [PATCH] Significant performace improvements on reiserfs systems, kupdated bugfixes Beau Kuiper
2001-09-20 12:16 ` Chris Mason
2001-09-20 15:20 ` Beau Kuiper
2001-09-20 16:15 ` Andreas Dilger
2001-09-20 16:22 ` Beau Kuiper
2001-09-21 20:12 ` Lehmann [this message]
2001-09-21 20:57 ` Rik van Riel
2001-09-21 22:50 ` Lehmann
2001-09-21 13:26 ` Matthias Andree
2001-09-22 18:38 ` Beau Kuiper
2001-09-22 19:32 ` Matthias Andree
2001-09-23 15:24 ` Chris Mason
2001-09-24 14:37 ` Stephen C. Tweedie
-- strict thread matches above, loose matches on Subject: below --
2001-09-20 17:23 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=20010921221225.A22402@schmorp.de \
--to=pcg@goof.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox