RE: [Syllable-kernel] Good artists borrow, great artists steal!

[Kristian V. <Kri...@an...>]

Jake Hamby wrote:
> One question:  is there any reason, licensing or otherwise, 
> for us not to also steal high-quality code from FreeBSD?

None at all, provided a) The semantics of the code fit with the
rest of the system without much work b) The code in question is
under the newer, non-advertsing, GPL compatable BSDL.

> Here are the particular pieces of BSD that I'm interested in:
> 
> * kernel malloc():  we need a better implementation than the 
> Linux 2.0.x malloc() we're using now.

Agreed.  The current allocator is slow and I believe, pretty
inefficient.

> * FreeBSD NFS implementation (unless NetBSD or OpenBSD is better?)

Some people would like to have NFS support, no doubt.  How smoothly
could we integrate NFS into Syllable?  An "NFS client" would be best
as a filesystem driver.  There is something in CVS at
syllable/misc/drivers/fs/nfs/ which claims to be an "NFS like" driver,
and a quick glance over the code looks as though runs with both a 
client and server thread.  I don't know anything at all about NFS
so I don't know how "NFS" like this is, or even if it's a good way
to it.

> * any relevant code from FreeBSD's TCP/IP stack, keeping intact our 
> Syllable-native TCP/IP implementation while adding any new 
> features or performance enhancing algorithms.

Sounds good to me.  Better support for various socket flags,
getsockopt() and setsockopt() would be good start.

-- 
Vanders
http://www.syllable.org
http://www.liqwyd.com


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________