From: Steven Cole <elenstev@mesatop.com>
To: Oleg Drokin <green@namesys.com>
Cc: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>,
Alex Zarochentsev <zam@namesys.com>,
reiserfs-dev@namesys.com, reiserfs-list@namesys.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: reiser4 snapshot for August 26th.
Date: 26 Aug 2003 13:51:22 -0600 [thread overview]
Message-ID: <1061927482.1666.36.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <20030826194321.GA25730@namesys.com>
On Tue, 2003-08-26 at 13:43, Oleg Drokin wrote:
> Hello!
>
> On Tue, Aug 26, 2003 at 09:36:07PM +0200, Felipe Alfaro Solana wrote:
> > > Disable "reiser4 system call" (CONFIG_REISER4_FS_SYSCALL) support, it is
> > > not ready.
> > [...]
> > arch/i386/kernel/built-in.o(.data+0x7c4): In function `sys_call_table':
> > : undefined reference to `sys_reiser4'
> > make[2]: *** [.tmp_vmlinux1] Error 1
> > make[1]: *** [vmlinux] Error 2
> > [...]
> > CONFIG_REISER4_FS=m
>
> Building as module is also not yet supported.
>
Fine, then here's a patch:
--- linux-2.6.0-test4-r4/fs/Kconfig.orig 2003-08-26 13:44:38.165059616 -0600
+++ linux-2.6.0-test4-r4/fs/Kconfig 2003-08-26 13:46:43.672979512 -0600
@@ -203,6 +203,9 @@
tristate "Reiser4 (EXPERIMENTAL very fast general purpose filesystem)"
depends on EXPERIMENTAL
---help---
+ Building as a module is not yet supported, so don't say 'M'
+ unless you're a developer.
+
Reiser4 is more than twice as fast for both reads and writes as
ReiserFS. That means it is four times as fast as NTFS by Microsoft.
(Proper benchmarks will appear in a few months at
Meanwhile, reiser4 seems to be working fine and is nice and fast.
I did a "time bk -r co" for the current 2.6 tree, and here
are the results for reiser4 and ext3 on 2.6.0-test4:
Reiser4:
real 1m55.077s
user 0m30.740s
sys 0m36.558s
Ext3:
real 3m48.438s
user 0m26.400s
sys 0m13.205s
Steven
next prev parent reply other threads:[~2003-08-26 19:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 10:22 Oleg Drokin
2003-08-26 18:20 ` Steven Cole
2003-08-26 18:26 ` Alex Zarochentsev
2003-08-26 19:36 ` Felipe Alfaro Solana
2003-08-26 19:43 ` Oleg Drokin
2003-08-26 19:51 ` Steven Cole [this message]
2003-08-26 20:05 ` Mike Fedyk
2003-08-26 20:13 ` Steven Cole
2003-08-26 20:26 ` Mike Fedyk
2003-08-26 20:25 ` Steven Cole
2003-08-26 20:30 ` Hans Reiser
2003-08-26 20:28 ` Hans Reiser
2003-08-26 19:53 ` Mike Fedyk
2003-08-26 19:57 ` how to log reiser and raid0 crash? 2.6.0-t4 Resident Boxholder
2003-08-26 22:20 ` Resident Boxholder
2003-08-27 10:35 ` Oleg Drokin
2003-08-28 7:28 ` Resident Boxholder
2003-08-26 18:38 ` reiser4 snapshot for August 26th Steven Cole
2003-08-26 19:22 ` Hans Reiser
2003-08-26 18:38 ` Oleg Drokin
2003-08-26 18:41 ` Hans Reiser
2003-08-26 18:41 ` Alex Zarochentsev
2003-08-26 19:14 ` Steven Cole
2003-08-28 11:46 ` Alex Zarochentsev
2003-08-28 15:12 ` Steven Cole
2003-08-28 16:33 ` Tupshin Harper
2003-08-26 19:15 ` Hans Reiser
2003-08-28 18:31 ` Vladimir Demidov
2003-08-26 21:28 ` Diego Calleja García
2003-08-27 7:38 ` Oleg Drokin
2003-08-27 5:52 ` Ian Wienand
2003-08-27 6:03 ` Yury Umanets
2003-08-27 11:19 ` Felipe Alfaro Solana
2003-08-27 15:54 ` Hans Reiser
2003-09-15 11:15 ` reiser4 snapshot 20030905 [OOPS] Maciej Soltysiak
2003-09-15 13:52 ` Nikita Danilov
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=1061927482.1666.36.camel@spc9.esa.lanl.gov \
--to=elenstev@mesatop.com \
--cc=felipe_alfaro@linuxmail.org \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@namesys.com \
--cc=reiserfs-list@namesys.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®