From: Hans Reiser <reiser@namesys.com>
To: "Markus Törnqvist" <mjt@nysv.org>
Cc: Alex Zarochentsev <zam@namesys.com>,
Will Smith <will@willsmith.org>,
reiserfs-list@namesys.com
Subject: Re: Benchmark : ext3 vs reiser4 and effects of fragmentation.
Date: Thu, 16 Sep 2004 19:29:27 -0700 [thread overview]
Message-ID: <414A4C07.8060802@namesys.com> (raw)
In-Reply-To: <20040916190019.GN26192@nysv.org>
Markus Törnqvist wrote:
>On Thu, Sep 16, 2004 at 10:38:31PM +0400, Alex Zarochentsev wrote:
>
>
>>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.
>>
>>
>
>What if it was like
>echo -n "Killer Algo by Zam" > /sys/fs/reiser4/hda1/repacker/algorithm
>or something to get rid of the risk of having two really separate
>mechanisms, and if it can't be in userspace either way...
>
>This is also probably related to what Nik said back in the days about
>an online-fsck being impossible :)
>
>
>
Online fsck is possible. Will do it for SuSE for 200k.;-)
It is a very serious task. I would not do it just for fun. It is,
however, feasible.
Hans
next prev parent reply other threads:[~2004-09-17 2:29 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
2004-09-16 19:00 ` mjt
2004-09-16 19:05 ` Chris Mason
2004-09-17 2:29 ` Hans Reiser [this message]
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=414A4C07.8060802@namesys.com \
--to=reiser@namesys.com \
--cc=mjt@nysv.org \
--cc=reiserfs-list@namesys.com \
--cc=will@willsmith.org \
--cc=zam@namesys.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 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.