Re: [lwip-users] lwIP performance with FreeRTOS

[Chris Ponder]

Thanks Simon,

Our application is really one of throughput, taking data in and spitting it out 
as UDP packets on the Ethernet as fast as we can. Unfortunately we do have 
other tasks that need to run while this is happening. Packets coming the other 
way number less than 100 for the 20,000 to 30,000 typical up-stream packet 
count.

Having said that, I am expecting performance degradation from the down-stream 
packets and other tasks. Hence my desire to ensure we have acceptable 
performance before introducing those elements. I have been wondering if there 
is a way of using the pbuf interface and encapsulating the whole lwIP plus send 
code in a single thread, but so far this has proved an elusive target.

Chris

-----Original Message-----
From: Simon Goldschmidt
Sent: 27 February 2012 18:34
To: Mailing list for lwIP users
Subject: Re: [lwip-users] lwIP performance with FreeRTOS

Chris Ponder wrote:

> Should I be looking more at lwIP (adding LWIP_TCPIP_CORE_LOCKING made quite 
> an improvement) or is this a FreeRTOS thing?

That's a good question, I'm afraid I can't answer it. I haven't used the 
netconn API when performance was needed, and I haven't ever benchmarked it.

Is the rest of your application the same? In other words, are you using the 
same pbuf/netbuf type (allocated and creating the data into it vs. sending by 
reference)? Are there many thread switches  from/to your application thread? 
Keep in mind that response packets are still passed into the tcpip_thread, so 
there may still be many (potentially slow) thread changes if you are using a 
ping-pong protocol where every packet sent results in a packet received (no 
matter how big that's, of course).

As to FreeRTOS, I can't comment on that, I haven't really used it, yet.

Simon

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users
********************************************************

The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. If you are not the addressee, any disclosure, reproduction,
copying, distribution, or other dissemination or use of this communication is
strictly prohibited. If you have received this transmission in
error please notify the sender immediately and then delete this e-mail.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted lost, destroyed, arrive late or
incomplete, or contain viruses.
The sender therefore does not accept liability for any errors or omissions
in the contents of this message which arise as a result of e-mail
transmission. If verification is required please request a hard copy
version.

********************************************************