Re: [lwip-devel] [bug #33604] Callback registering functions don't check for a legal socket state

[Cameron Gutman]

I agree that it isn't the ideal network stack for ReactOS. We have one based on 
the OSKit project but it required a lot of nasty hacks and it crashes 
frequently. I figured we'd take a performance hit but it was worth the 
stability and upgradability. We have the IP, UDP, and Raw IP layers implemented 
in our own code (which works fairly well) but TCP is a complicated beast and 
we've always relied on a 3rd party library to provide it. lwIP will also help 
because as lwIP's IPv6 implementation matures, it can be integrated into 
ReactOS alongside our IPv4-only implementation. I think for our alpha status 
this will do but later we'll need to find another solution for the long term 
before we reach beta status.


Cameron Gutman

On Jun 25, 2011, at 5:51 AM, address@hidden wrote:

> Cameron Gutman wrote:
>> This issue was one that I ran into when integrating lwIP into the network
>> stack for the ReactOS project.
> An interesting task. I'm not too familiar with the current state of ReactOS, 
> but I'm not too convinced lwIP is the correct network stack for such a system.
> 
> Not only might multithreaded usage be a performance problem, but the fact 
> that lwIP is optimized for size rather than speed might impact performance, 
> too. For example, unsorted lists are used in many places since lwIP is 
> optimized for a small number of connections. This does not scale very well 
> for a full blown OS with many parallel connections.
> 
> However, unless this does not limit you too much, I'm still interested in any 
> optimizations you find which are in line with the original target of lwIP.
> 
> Simon
> 
> _______________________________________________
> lwip-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/lwip-devel