[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: Atte Kojo
Subject: [lwip-devel] [task #6935] Problems to be solved with the current socket/netconn API
Date: Thu, 24 May 2007 13:02:25 +0000
User-agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.6 (like Gecko)

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

I vote for re-implementing the sockets API from scratch directly on top of
the raw API using mutexes for synchronization.

Actually, what I'd really like is that Kieran wouldn't have to use phrases
"lwIP is not thread-safe" and "to get good performance, you should use raw
API" ever again on lwip-users ;-).

> I agree speed is not the main goal for lwIP.

Me too, but if everybody and their dog are running lwIP at wire-speeds using
the raw API, getting good performance using a sequential API shouldn't be
*that* difficult.

Maybe integrate this with tasks #6849 and #6863, and suddenly we might end up
with the smallest, fastest and meanest embedded TCP/IP stack ever ;-D.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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