From: Lexington Luthor <Lexington.Luthor@gmail.com>
To: reiserfs-list@namesys.com
Subject: Re: Another article abour Reiser4 on linux.com
Date: Sun, 06 Aug 2006 18:06:53 +0100 [thread overview]
Message-ID: <eb57je$cll$1@sea.gmane.org> (raw)
In-Reply-To: <200608061515.28467.bernd-schubert@gmx.de>
Bernd Schubert wrote:
> Well, by having a FUSE port just more users would use reiser4, which might
> increase the force to the linux distributors to include reiser4 into their
> kernel versions.
>
I don't think reiser4 would gain many users if it is crippled by being
in userspace. All the lazy flushing and aggressive caching become
useless if it cannot interact directly with the pagecache and respond to
memory pressure. Would you tolerate a 2GB process just to run a
filesystem? Thats what reiser4 can do if it is in the kernel, and
silently give back memory only when needed.
> Regarding the speed, I understand that its slower with FUSE, I was also deeply
> impressed when I read this
> (http://sourceforge.net/mailarchive/forum.php?thread_id=23836054&forum_id=2697)
>
> But being twice as fast as ext3 is enough currently. It's even faster than
> xfs what I use. Sometimes I'm quite suprised why something is so fast when
> I realize that it was actually ntfs-3g :-)
>
Those micro-benchmarks do not represent anything like normal use. NTFS
is probably the most complicated filesystem on the planet, so there is
zero chance that a *working* implementation of it can outperform
something like XFS... even reiser4 barely beats XFS in many situations
(actually slower than XFS for heavy local rsync activity).
- LL
next prev parent reply other threads:[~2006-08-06 17:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 12:55 Another article abour Reiser4 on linux.com Tassilo Horn
2006-08-05 14:55 ` David Masover
2006-08-05 16:17 ` Maciej Sołtysiak
2006-08-05 16:22 ` Maciej Sołtysiak
2006-08-05 18:07 ` Clay Barnes
2006-08-05 21:40 ` David Masover
2006-08-06 0:44 ` Clay Barnes
2006-08-06 1:39 ` David Masover
2006-08-06 2:14 ` TongKe Xue
2006-08-06 2:51 ` David Masover
2006-08-06 4:07 ` TongKe Xue
2006-08-06 8:20 ` Hans Reiser
2006-08-06 11:04 ` Bernd Schubert
2006-08-06 12:41 ` Lexington Luthor
2006-08-06 13:15 ` Bernd Schubert
2006-08-06 17:06 ` Lexington Luthor [this message]
2006-08-06 19:17 ` David Masover
2006-08-06 19:21 ` TongKe Xue
2006-08-09 8:07 ` Hans Reiser
2006-08-06 9:19 ` Hans Reiser
2006-08-06 16:26 ` Clemens Eisserer
2006-08-06 22:55 ` Bruce Byfield
2006-08-09 8:28 ` Hans Reiser
2006-08-09 9:47 ` Andreas Schäfer
2006-08-09 15:51 ` David Masover
2006-08-09 18:38 ` Bruce Byfield
2006-08-09 17:37 ` Hans Reiser
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='eb57je$cll$1@sea.gmane.org' \
--to=lexington.luthor@gmail.com \
--cc=reiserfs-list@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.