os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Kirk has updated dump to save extended attributes, so remove the entry

Browse source 
from the list.
-  Add more info to the libumem entry.
-  Move the msdosfs entry to the correct (alphabetically) place.

Submitted by:   netchild
This commit is contained in:
Joel Dahl 2007-02-26 17:32:53 +00:00
parent 70904653e0
commit a207989817
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=29663
1 changed files with 44 additions and 39 deletions
Download patch file Download diff file Expand all files Collapse all files

83
en/projects/ideas/index.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/projects/ideas/index.sgml,v 1.91 2007/02/21 23:09:54 joel Exp $">
<!ENTITY date "$FreeBSD: www/en/projects/ideas/index.sgml,v 1.92 2007/02/26 15:49:17 rwatson Exp $">
<!ENTITY title "FreeBSD list of projects and ideas for volunteers">
<!ENTITY % navinclude.developers "INCLUDE">
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -51,10 +51,10 @@
<h3>File System</h3>
<ul>
<li><a href="#p-extenddump">Extend dump/restore (extended attributes)</a></li>
<li><a href="#p-msdosfs">FAT (msdosfs) infrastructure work</a></li>
<li><a href="#p-extenddump">Improve the performance of dump/restore</a></li>
<li><a href="#p-mdfs">MDFS lockups</a></li>
<li><a href="#p-tmpfs">TMPFS</a></li>
<li><a href="#p-msdosfs">FAT (msdosfs) infrastructure work</a></li>
</ul>
<h3>Kernel</h3>
@ -142,18 +142,39 @@
<!- File System ->
<!------------------------------------------------------------------>
<a name="p-msdosfs"></a>
<h2>FAT (msdosfs) infrastructure work</h2>
<p><strong>Technical Contact</strong>: <a
href="mailto:rwatson@FreeBSD.org">&a.rwatson;</a></p>
<p>The FreeBSD FAT implementation, msdosfs, offers scope for a number of
projects:</p>
<ul>
<li>General cleanup.</li>
<li>Introduce appropriate locking to make the file system operate without
the Giant lock (MPSAFE).</li>
<li>Make msdosfs robust in the presence of unexpected disk removal, since
it is frequently used with removable devices.</li>
</ul>
<p>It is unclear to what extent the last of these items, arguably the most
useful, will require modifying surrounding infrastructure such as BIO,
GEOM, and VM.</p>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Strong C programming skills.</li>
<li>Familiarity with concurrent programming techniques.</li>
<li>Familiarity with FAT file system layout.</li>
<li>Familiarity with virtual file system and virtual memory.</li>
</ul>
<hr>
<a name="p-extenddump"></a>
<h2>Extend dump/restore (extended attributes)</h2>
<p>The UFS2 file system in FreeBSD supports extended attributes. Extended
attributes are meta-data associated with vnodes representing files and
directories. Unfortunately dump and restore do not backup or restore
such attributes. People interested in this should contact <a
href="mailto:mckusick@FreeBSD.org">&a.mckusick;</a>.</p>
<p>Furthermore a performance evaluation of the split cache (as is) and
an unified cache (like e.g. NetBSD) would be interesting. More details
in <a
<h2>Improve the performance of dump/restore</h2>
<p>A performance evaluation of the split cache (as is) and an unified cache
(like e.g. NetBSD) would be interesting. More details in <a
href="http://lists.freebsd.org/pipermail/freebsd-hackers/2007-February/019666.html">
this</a> mail to the hackers mailing-list.</p>
this</a> mail to the hackers mailing list. Additional improvements are
welcome too.</p>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Knowledge of C programming.</li>
@ -209,32 +230,6 @@
<hr>
<a name="#p-msdosfs"></a>
<h2>FAT (msdosfs) infrastructure work</h2>
<p><strong>Technical Contact</strong>: <a
href="mailto:rwatson@FreeBSD.org">&a.rwatson;</a></p>
<p>The FreeBSD FAT implementation, msdosfs, offers scope for a number of
projects:</p>
<ul>
<li>General cleanup.</li>
<li>Introduce appropriate locking to make the file system operate without
the Giant lock (MPSAFE).</li>
<li>Make msdosfs robust in the presence of unexpected disk removal, since
it is frequently used with removable devices.</li>
</ul>
<p>It is unclear to what extent the last of these items, arguably the most
useful, will require modifying surrounding infrastructure such as BIO,
GEOM, and VM.</p>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Strong C programming skills.</li>
<li>Familiarity with concurrent programming techniques.</li>
<li>Familiarity with FAT file system layout.</li>
<li>Familiarity with virtual file system and virtual memory.</li>
</ul>
<hr>
<!------------------------------------------------------------------>
<!- Kernel ->
<!------------------------------------------------------------------>
@ -1249,6 +1244,16 @@ New tests must be created; existing tests must be completed and updated.
<p>Solaris 9 and later versions include <code>libumem</code>, a user
space slab allocator that includes debugging features we may want to
have on FreeBSD too.</p>
<p><a href="mailto:leeym@FreeBSD.org">&a.leeym;</a> has a port of
the <a href="http://sourceforge.net/projects/umem">Linux port</a>. He
is looking for someone who is interested in benchmarking, testing, or
evaluating his port.</p>
<p><a href="mailto:jasone@FreeBSD.org">&a.jasone;</a> has a benchmark
suite at <a
href="http://people.freebsd.org/~jasone/jemalloc/benchmarks/benchmarks.tbz">
here</a>. A description of the benchmark can be found in his
<a href="http://people.freebsd.org/~jasone/jemalloc/bsdcan2006/jemalloc.pdf">
jemalloc paper</a></p>
<p>Online references for <code>libumem</code> are (in suggested reading
order):</p>
<ul>