Re: [lwip-users] LWIP/WIN32 UDP performance (throughtput)

[Bill Auerbach]

Stas,

 

Res, RAW API and NO_SYS=1.  You don’t need threads with RAW API if you have a “big loop” type of program that spins processing lwIP timers and other system events.

 

Single threaded?  Yes and no I guess.  We use a cooperative RTOS so there are many tasks, but one task handles Ethernet, lwIP and its callbacks.  The other threads (tasks) do send TCP data but being cooperative in nature there is never a worry as to when they do need to send something.  Being mostly event driven, lwIP’s task gets 99%-interrupt processing time of CPU time so there is always all the bandwidth we need.  This is a real-time system and can push 50-60MB/S (TCP) and at this speed 30% of the processor is then processing interrupts (not Ethernet interrupts – they are polled).

 

Bill

 

From: address@hidden [mailto:address@hidden On Behalf Of Zayaz Volk
Sent: Tuesday, February 07, 2012 11:32 AM
To: address@hidden
Subject: Re: [lwip-users] LWIP/WIN32 UDP performance (throughtput)

 

Bill,
Do you use the RAW API with NO_SYS=1, i.e. singe threaded ?
Don't you need another threads to be able to send a data over ethernet ?
Is your application single threaded ?

I guess i would need an ability to send a data over ethernet from other threads as well, so NETCONN might be my "lowest" possible API, or did i miss something ?
If NETCONN API is the "lowest" way to run a lwip in multi threaded environment, did somebody tried to profile this API on PC or its own Hardware (i.e. did somebody use an lwip in multi threaded environment) ?
What was the outcome ?

Thanks,
Stas

---