| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
| |||
| |||
| Hi, I have measured TCP/IP throughput on H4 board and I have really poor throu= ghputs. I did the measurements with the Ethernet port and a WLAN SDIO card and I ha= ve got the same low throughputs. This seems to not be related to HW. The RTT of the ping is 86 milliseconds between a PC and the H4 board wherea= s it takes less than 1ms between 2 PCs. Therefore, the H4 board takes 85 ms to process the = ping. Too much for an ARM11 running at 300Mhz. For the TCP traffic, the PC sends its TCP window (9 TCP data frames) and th= e H4 board replies (with an TCP ACK) 300 ms after the last received frame. Very huge delay making a = low TCP/IP throughput. Are there specific settings to apply for making the TCP/IP stack more perfo= rmant ? Is it possible that TCP/IP stack is a low priority process/thread by defaul= t ? Best regards, Franck |
|
#2
| |||
| |||
| franckf_df8866 wrote: > Very huge delay making a low > TCP/IP throughput. Are there specific settings to apply for making the TCP/IP > stack more performant ? Is it possible that TCP/IP stack is a low priority > process/thread by default ? Best regards, Franck The cause is probably in the H4 Ethernet hw or driver. My experience on earlier boards was that it was very easy to block all communication just by flood pinging the device: as long as ping is running, the TCP/IP stack doesn't see a single packet... (e.g. there is nothing that could be done at TCP/IP level). When flooding is stopped, the stack gets a burst of X first packets from the flood. |
|
#3
| |||
| |||
| bq. {color:#999999} \\ The cause is probably in the H4 Ethernet hw or drive= r. My experience on \\ earlier boards was that it was very easy to block al= l communication just \\ by flood pinging the device: as long as ping is run= ning, the TCP/IP \\ stack doesn't see a single packet... (e.g. there is not= hing that could \\ be done at TCP/IP level). \\ {color} {color:#000000}Just for information, I did not run ping and TCP/IP streams = simultaneously. The TCP/IP stream runs when ping is stopped. On the other hand, I have got the same very low = throughput with the H4 Ethernet port or a WLAN SDIO card. Therefore, I think this should no= t be related to the H4 Ethernet HW or SDIO HW. {color}bq. |
![]() |
| Thread Tools | |
| Display Modes | |
In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.