From: Alex Zarochentsev <zam@namesys.com>
To: "Markus TЖrnqvist" <mjt@nysv.org>
Cc: Will Smith <will@willsmith.org>, reiserfs-list@namesys.com
Subject: Re: Benchmark : ext3 vs reiser4 and effects of fragmentation.
Date: Thu, 16 Sep 2004 22:38:31 +0400 [thread overview]
Message-ID: <20040916183831.GL5137@backtop.namesys.com> (raw)
In-Reply-To: <20040916155248.GM26192@nysv.org>
On Thu, Sep 16, 2004 at 06:52:48PM +0300, Markus Törnqvist wrote:
> On Thu, Sep 16, 2004 at 07:38:36PM +0400, Alex Zarochentsev wrote:
>
> >We are not going to add more intelligence to the in-kernel repacker module but
> >design an interface between repacker and user-space programs and implement
> >reisizing alg. in user-space.
>
> This sounds a bit fishy; is it about having two repackers then?
> One in kernelspace and one in userspace?
> Will the kernelspace one be obsoleted?
on-line defragmenter requires its part to be in kernel space. at least node
locks cannot be exported _safely_ to the user space, I think.
>
> >> >unmergable units shouldn't be problem for the reiser4 kernel code.
> >> What are their significance; what do they mean?
> >two extent units (start1, len1), (start2, len2) can be merged into one (start1,
> >len1 + len2) because start1 + len1 == start2. I think no reiser4 kernel code
> >depends on that mergable extents do not exist.
>
> Unmergable units are then (start1 + len1) != start2 because the repacker
> messed this up?
it can be so because of regular fs activity. Current block allocation (and
flush algorithm) is not good for appending to existing files. A free space
after well-allocated reiser4 tree or a well-allocated part of the reiser4 tree
(in case of repacker) can be allocated randomly between new data blocks for
those files.
My opinion -- reiser4 is good in (re)allocating slums. In case of allocation
many small slums it may be not effective. The idea of the reiser4 repacker is
to create large slums and allow flush code to do its work.
>
> The kernel finds the extent units from their "old places" without optimizing
> them to one unit?
in some places, yes, those extents will be merged into one. but i agree, we
can't allow number of those units to grow unlimitedly. IMHO it would be enough
if the repacker will scan units and do what now is done by fsck -- merging of
mergeable units.
> --
> mjt
--
Alex.
next prev parent reply other threads:[~2004-09-16 18:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 22:02 Benchmark : ext3 vs reiser4 and effects of fragmentation Will Smith
2004-09-16 8:52 ` Alex Zarochentsev
2004-09-16 13:08 ` mjt
2004-09-16 14:50 ` Will Smith
2004-09-16 15:03 ` mjt
2004-09-16 17:16 ` Hans Reiser
2004-09-16 15:38 ` Alex Zarochentsev
2004-09-16 15:52 ` mjt
2004-09-16 17:26 ` Hans Reiser
2004-09-16 18:38 ` Alex Zarochentsev [this message]
2004-09-16 19:00 ` mjt
2004-09-16 19:05 ` Chris Mason
2004-09-17 2:29 ` Hans Reiser
2004-09-17 17:01 ` Philippe Gramoullé
2004-09-16 15:38 ` Christian Mayrhuber
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=20040916183831.GL5137@backtop.namesys.com \
--to=zam@namesys.com \
--cc=mjt@nysv.org \
--cc=reiserfs-list@namesys.com \
--cc=will@willsmith.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.