RE : [lwip-devel] brain storming about "socket2"

[Frédéric BERNON]

> * Coming back to why I am concerned about sockets in lwip: I fully 
> realize that an open source project is what everyone contributes to 
> it, but I get the feeling that most of you active developers are not 
> using the socket API,

I can tell I use it in my projects, and the code is stable. 1.3.0 add lots of 
functions to Socket API, but about performance, if the standard BSD socket API 
design cause lot of memcpy, another important problem is the "sequential api" 
(on which is based "netconn"): the fact that any operations cause a "task 
switching" to the "tcpip_thread" doesn't help to get high performance. That 
what I got when I did my tests, and when we introduced the "socket2.c" in "task 
#6994 : Redesign Socket Layer with LWIP_TCPIP_CORE_LOCKING".

Of course, adding some extra-sockets API to avoid some memcpy can help. We have 
talk about that in task#6994. I changed is as "Private" to avoid to have lot of 
questions about it, since at this time, only Simon and me worked on it.

But I don't have lot of time to continue this task, so, if Simon is agree, we 
can change it as "Public". But remember it's just a first "draft" with lot of 
work to do. I'm not even sure it's always directly compatible with current CVS.

  
====================================
Frédéric BERNON 
HYMATOM SA 
Chef de projet informatique 
Microsoft Certified Professional 
Tél. : +33 (0)4-67-87-61-10 
Fax. : +33 (0)4-67-70-85-44 
Email : address@hidden 
Web Site : http://www.hymatom.fr 

Plan d'accès au siège social 

====================================
P Avant d'imprimer, penser à l'environnement

Frédéric BERNON.vcf
Description: Frédéric BERNON.vcf