From: "Clemens Eisserer" <linuxhippy@gmail.com>
To: reiserfs-list@namesys.com
Subject: Re: State of the Reiser4 FS
Date: Tue, 14 Mar 2006 16:32:32 +0100 [thread overview]
Message-ID: <194f62550603140732j6ef10757j@mail.gmail.com> (raw)
In-Reply-To: <1142336718.7415.55.camel@tribesman.namesys.com>
> AFAIK, the most recent reason why reiser4 does not get included is that
> reiser4 developers have to change reiser4 to use generic code to
> implement read/write.
> AFAICS, reiser4 developers do not work on that.
Has this really become a reason to not include reiser4 into mainline?
I also don't see a reason for that - at least it would bind reiser4
more close to linux making ports to other OS harder.
Furthermore if it would decrease performance its simply no way to go.
(btw. I think this could be a way to generate some revenue - I think
there is demand for a modern fs which is supported by both, windows
and linux).
lg Clemens
next prev parent reply other threads:[~2006-03-14 15:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 10:41 State of the Reiser4 FS Avuton Olrich
2006-03-14 11:45 ` Vladimir V. Saveliev
2006-03-14 15:32 ` Clemens Eisserer [this message]
2006-03-15 7:14 ` Hans Reiser
2006-03-15 8:57 ` Andreas Schäfer
2006-03-15 18:29 ` Hans Reiser
2006-03-15 19:27 ` Andreas Schäfer
2006-03-15 21:08 ` Andreas Dilger
2006-03-16 0:58 ` 4k at a time only works well for an OS that does less per iteration than Linux does Hans Reiser
2006-03-15 19:45 ` State of the Reiser4 FS Jonathan Briggs
2006-03-15 20:43 ` Hans Reiser
2006-03-15 21:25 ` Andreas Schäfer
2006-03-15 8:45 ` Hans Reiser
2006-03-15 12:59 ` Avuton Olrich
2006-03-15 18:33 ` Hans Reiser
2006-03-26 11:27 ` 2.6.16 patch jp
2006-03-27 17:27 ` jp
2006-03-28 11:42 ` Vladimir V. Saveliev
2006-03-28 12:54 ` Tassilo Horn
2006-03-28 17:12 ` Danny Milosavljevic
2006-03-28 18:00 ` Tassilo Horn
2006-03-28 23:22 ` Jake Maciejewski
2006-03-27 20:10 ` Marcus Furlong
2006-03-27 19:44 ` Tassilo Horn
2006-03-27 21:32 ` Marcus Furlong
2006-03-27 20:41 ` Tassilo Horn
2006-03-27 21:29 ` Tassilo Horn
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=194f62550603140732j6ef10757j@mail.gmail.com \
--to=linuxhippy@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.