[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [task #6935] Problems to be solved with the current socket/

From: Frédéric Bernon
Subject: [lwip-devel] [task #6935] Problems to be solved with the current socket/netconn API
Date: Fri, 01 Jun 2007 08:29:58 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv: Gecko/20070515 Firefox/

Follow-up Comment #13, task #6935 (project lwip):

Another thing with the current socket layer (it's not true for netconn
layer): "struct netbuf" is just used like a "wrapper" of a "struct pbuf" with
addr & port fields. In socket layer, lot of netbuf functions are not used. And
each time that a packet have to be exchange between socket layer & api_msg,
there is an netbuf allocation, initialization & free.

If we redesign the socket layer, I propose to remove any code using netbuf
and to replace that by adding "addr & port" fields directly in pbuf struct. I
don't think that the memory use will be increase (because even if we lost
memory in each pbuf, we gain the netbuf memp & functions code).


Reply to this item at:


  Message posté via/par Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]