From: <pcg@goof.com ( Marc) (A.) (Lehmann )>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Significant performace improvements on reiserfs systems, kupdated bugfixes
Date: Sat, 22 Sep 2001 00:50:51 +0200 [thread overview]
Message-ID: <20010922005051.A5360@schmorp.de> (raw)
In-Reply-To: <20010921221225.A22402@schmorp.de> <Pine.LNX.4.33L.0109211757050.19147-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0109211757050.19147-100000@imladris.rielhome.conectiva>
On Fri, Sep 21, 2001 at 05:57:36PM -0300, Rik van Riel <riel@conectiva.com.br> wrote:
> On the contrary, when you have a bunch of small files to sync
> you just allocate them next to each other and flush them all
> at once ;)
Different layer really: The idea was to sync blocks contiguous to the
dirty block we want to sync (regardless of filesystem, i.e. similar to
the elevator which also works at abelow-the-fs-level). (Allocated) block
numbers are necessary for this to work.
(but i don't know how relevant this is in practise. I think it might gain
a lot, though, but that doesn't mean much ;)
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@goof.com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
next prev parent reply other threads:[~2001-09-21 22:51 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
2001-09-21 20:57 ` Rik van Riel
2001-09-21 22:50 ` Lehmann [this message]
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=20010922005051.A5360@schmorp.de \
--to=pcg@goof.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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