[openbeosnetteam] Re: FreeBSD vs. our stack
- From: "Joseph Liu" <froseph@xxxxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Fri, 2 Jun 2006 16:05:44 -0700
Hi,
Just trying to understand waht the proposal is.
On 6/2/06, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx> wrote:
Hi there,
Waldemar and I talked a bit and here is what we came up with:
According to Waldemar, our current networking stack is still very close
to a BSD stack which could ease the effort of porting FreeBSD modules
into it. Also according to Waldemar, he has little hope that we could
or should use any of the code in our repository right now. While my
impression of the code was similar, it has been some years since I
looked at it (during David's active time).
In any way, what needs to be done first is that someone starts at the
very ground (ie. packet and memory management, a.k.a. mbufs and their
handling) of our current stack and works his way up in layers and
modules. Step by step the existing code can either be replaced with
FreeBSD code or fixed so that it becomes usable. Everything above the
current working set doesn't even need to be built.
The only things that we definitely need to keep are the
net_stack_driver, the ethernet legacy code, and the userland testing
stuff (BONE only). The ethernet code probably needs most of the work
and should be better separated from the rest.
Are you proposing to mix and match FBSD code and current Haiku code
with regards to the netstack internals? Would it be easier or less
confusing to start with FBSD and port it entirely to Haiku?
--Joe
- Follow-Ups:
- [openbeosnetteam] Re: FreeBSD vs. our stack
- From: Axel Dörfler
- References:
- [openbeosnetteam] FreeBSD vs. our stack
- From: Axel Dörfler
Other related posts:
- » [openbeosnetteam] FreeBSD vs. our stack
- » [openbeosnetteam] Re: FreeBSD vs. our stack
- » [openbeosnetteam] Re: FreeBSD vs. our stack
- » [openbeosnetteam] Re: FreeBSD vs. our stack
- » [openbeosnetteam] Re: FreeBSD vs. our stack
- » [openbeosnetteam] Re: FreeBSD vs. our stack
- » [openbeosnetteam] Re: FreeBSD vs. our stack
- » [openbeosnetteam] Re: FreeBSD vs. our stack
- » [openbeosnetteam] Re: FreeBSD vs. our stack
- » [openbeosnetteam] Re: FreeBSD vs. our stack
- » [openbeosnetteam] Re: FreeBSD vs. our stack
- » [openbeosnetteam] Re: FreeBSD vs. our stack
- » [openbeosnetteam] Re: FreeBSD vs. our stack
- » [openbeosnetteam] Re: FreeBSD vs. our stack
- » [openbeosnetteam] Re: FreeBSD vs. our stack
- » [openbeosnetteam] Re: FreeBSD vs. our stack
Hi there,
Waldemar and I talked a bit and here is what we came up with:
According to Waldemar, our current networking stack is still very close to a BSD stack which could ease the effort of porting FreeBSD modules into it. Also according to Waldemar, he has little hope that we could or should use any of the code in our repository right now. While my impression of the code was similar, it has been some years since I looked at it (during David's active time).
In any way, what needs to be done first is that someone starts at the very ground (ie. packet and memory management, a.k.a. mbufs and their handling) of our current stack and works his way up in layers and modules. Step by step the existing code can either be replaced with FreeBSD code or fixed so that it becomes usable. Everything above the current working set doesn't even need to be built. The only things that we definitely need to keep are the net_stack_driver, the ethernet legacy code, and the userland testing stuff (BONE only). The ethernet code probably needs most of the work and should be better separated from the rest.
Are you proposing to mix and match FBSD code and current Haiku code with regards to the netstack internals? Would it be easier or less confusing to start with FBSD and port it entirely to Haiku?
- [openbeosnetteam] Re: FreeBSD vs. our stack
- From: Axel Dörfler
- [openbeosnetteam] FreeBSD vs. our stack
- From: Axel Dörfler