|
发表于 2004-8-20 10:33:57
|
显示全部楼层
2.6.8.1-mm2
- Added the reiser4 filesystem. Please give it a whizz. Please Cc
[email protected] on any problem reports. (It spits a bunch of
warnings on 64-bit compiles - that'll be fixed)
Here's a little questionnaire which Hans filled out for me, to help people
get started:
- A really short guide to how to get up and running with this filesystem.
Reiser4 is a file system based on dancing tree algorithms, and
is described at http://www.namesys.com. One should be able to get it
up and running just like any of the other filesystems supported by
Linux. Configure it to be compiled either builtin or as a module.
Create reiser4 filesystem with mkfs.reiser4, mount and use it. More
detailed info can be found at
http://thebsh.namesys.com/snapshots/LATEST/READ.ME.
- The direct URL which people use to obtain the mkfs tool for this
filesystem. Also fsck and anything else.
Reiser4 userland tools can be obtained at
ftp://ftp.namesys.com/pub/reiser4progs.
ftp://ftp.namesys.com/pub/reiser4progs/README contains detailed
instructions on how to compile and install these tools. Also all
reiser4 progs have man pages.
- Any known shortcomings, caveats, etc.
Reiser4 has been tested on i386 yet only. Quota support is
not ready yet. Should be ready soon. Reiser4 was tested extensively,
and we got to where the mailing list was not able to hit any bugs, but
then we told people that, got an order of magnitude increase in users,
and they are able to hit bugs that we are working on now.
Reiser's Law of Software Engineering: Each order of magnitude
increase in users finds more bugs, in a quantity equal to the previous
order of magnitude increase in users. Success for software developers
is measured by how long the frustration lasts.
Only the very core functionality is working. Exotic plugins,
an API for multiple operation transactions and accessing multiple
small files in one syscall, compression, inheritance, all have been
postponed until after the core functionality is shipped. The
compression plugin needs a code review before anyone should use it.
- A statement on compatibility with reiserfs3 filesytems.
To upgrade from reiserfs V3 to V4, use tar, or sponsor us to
write a convertfs.
- Bear in mind that people will immediately benchmark this filesytem,
and first impressions count. Now is your chance to communicate any tuning
guidelines, mount options or whatever which you'd like people to
understand BEFORE they start publishing benchmark info.
Reiser4 is not tuned for fsync/sync/O_SYNC performance yet.
If you see results that are much different from those at
www.namesys.com/benchmarks.html, let us know. If you see performance
characteristics that don't quite make sense, email
[email protected], such things are always of interest.
reiser4 is not tuned for mmaping and dirtying more than
physical ram like IOzone does. This is quite different in its code
path from writing and dirtying more than physical ram. There are
those who think that what IOZone does is rarely done by real programs,
and therefor we should not bother to optimize what it does. All I
know is, this month we are not optimized for it.
Please consider its space savings when you benchmark it also. |
|