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

Some updates:

Browse source 
- FireWire is locked now.
 - Doug Rabson is working on a kernel level lockd, sponsored by Isilon.
   The code looks promising, as such remove the lockd entries until we
   can identify if there needs to be a replacement / some help or not.
 - ext2fs with gjournal would be incompatible with Linux, this is not
   desired. Scratch the gjournal part and reword to look out for
   improvements we could obtain from NetBSD.
 - iSCSI is in FreeBSD now.
 - Comment out the sensors framework entry until we have a definitive
   decission regarding the architecture we want to have for FreeBSD.

Suggested/noticed by:	rwatson
This commit is contained in:
Alexander Leidinger 2008-03-06 12:59:33 +00:00
parent db1069f015
commit 7086b79779
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=31619
1 changed files with 8 additions and 90 deletions
Download patch file Download diff file Expand all files Collapse all files

98
en/projects/ideas/ideas.xml
View file

@ -15,7 +15,7 @@ Ideas//EN"
<ideas>
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd">
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.35 2008/02/28 22:15:44 brooks Exp $
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.36 2008/02/29 01:45:08 trhodes Exp $
</cvs:keyword>
</cvs:keywords>
@ -86,7 +86,7 @@ Ideas//EN"
</idea>
<idea id="portext2fs">
<title>Port NetBSD's ext2fs and teach it to use gjournal</title>
<title>Analyze NetBSD's ext2fs regarding valuable improvements</title>
<desc><p>FreeBSD has an implementation of the ext2fs filesystems
but it contains some files under the GPL which make it undesirable,
@ -94,13 +94,10 @@ Ideas//EN"
simple but practical filesystem and NetBSD has had for <a
href="http://ezine.daemonnews.org/200006/ext2fs.html">a while</a>
an <a href="http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/ufs/ext2fs/">
implementation</a> based on UFS1 sources. Linux has several
interesting filesystems but most distributions seem to be gravitating
towards ext3fs, which supports the same on-disk format as ext2fs and
adds journalling. Porting NetBSD's ext2fs and adding support for in
gjournal (if possible) would make an excellent combination. Other
desirable possibilities would be to implement EA/ACLs and to use
it as root filesystem.</p>
implementation</a> based on UFS1 sources. The NetBSD implementation
needs to be analyzed regarding features and performance. If it is
on par or better with our GPLed implementation, it should be
ported to FreeBSD.</p>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Knowledge of C programming.</li>
@ -516,50 +513,6 @@ href="http://info.iet.unipi.it/~luigi/FreeBSD/linux_bsd_kld.html">here</a>.</p>
</desc>
</idea>
<idea id="iscsi">
<title>iSCSI</title>
<desc>
<p><strong>Technical contact</strong>: <a
href="mailto:danny@cs.huji.ac.il">Danny Braniss</a></p>
<p>Danny Braniss has been working on an iSCSI stack for FreeBSD for some time
now. His work is in Perforce, and he has posted several patch sets
and had numerous discussions on the mailing lists.</p>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Ability to read and understand foreign C code.</li>
<li>Ability to write C code.</li>
<li>Knowledge about (i)SCSI/CAM.</li>
</ul>
</desc>
</idea>
<idea id="firewire-locking">
<title>Locking the FireWire device driver</title>
<desc><p><strong>Technical contact</strong>: <a href="mailto:simokawa@FreeBSD.ORG">Hidetoshi Shimokawa</a></p>
<p>The IEEE1394 (a.k.a. FireWire) device driver in FreeBSD is
still under the Giant lock. The FireWire driver consists of
several parts (fwohci, firewire, sbp, fwe and fwip) and
they all need to be locked.</p>
<p><strong>Goals</strong>:</p>
<ul>
<li>Protect the driver by SMP locks and remove the Giant lock
from the driver.</li>
</ul>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Knowledge of kernel programming.</li>
<li>Knowledge of device drivers.</li>
<li>Knowledge of SMP locking.</li>
</ul>
</desc>
</idea>
<idea id="busalloc" class="soc">
<title>New bus_alloc_resources() API</title>
@ -634,6 +587,7 @@ they all need to be locked.</p>
</desc>
</idea>
<!--
<idea id="sensors">
<title>Add support for the sensors framework to more drivers</title>
@ -649,6 +603,7 @@ they all need to be locked.</p>
</ul>
</desc>
</idea>
-->
<idea id="trussprocfs">
<title>Remove procfs dependencies</title>
@ -850,43 +805,6 @@ they all need to be locked.</p>
</desc>
</idea>
<idea id="nfslockdsemantics">
<title>NFS Lockd (improve semantics)</title>
<desc>
<p><strong>Technical contact</strong>: <a
href="mailto:alfred@FreeBSD.org">Alfred Perlstein</a></p>
<ul>
<li>Improve the semantics of the NFS lockd in FreeBSD. Apple has made
certain enhancements that can be leveraged in our code base.</li>
<li>Implement state recovery in the lockd.</li>
</ul>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Good knowledge of C.</li>
</ul>
</desc>
</idea>
<idea id="nfslockdkernel">
<title>NFS Lockd (kernel implementation)</title>
<desc>
<p><strong>Technical contact</strong>: <a
href="mailto:alfred@FreeBSD.org">Alfred Perlstein</a></p>
<p>Moving the lockd implementation into the kernel provides several key
performance and semantic improvements.</p>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Good knowledge of C.</li>
<li>Good understanding of NFS.</li>
<li>Good understanding of locking.</li>
<li>Good understanding of RPC.</li>
<li>Good understanding of kernel level networking.</li>
</ul>
</desc>
</idea>
<idea id="pfnetgraph">
<title>pf and netgraph interaction</title>