lwip-users
[Top][All Lists]
Advanced

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

[lwip-users] A lot of packets lost by ping


From: Amir Bukhari
Subject: [lwip-users] A lot of packets lost by ping
Date: Fri, 4 Nov 2005 11:45:04 +0100

I have got lwip to work with uCOS-II/MPC5200 (using Bestcomm DMA), but I
have some performance issue.

When I ping my uC from a another computer I got response but slowly here is
some of this output

################
address@hidden /tftpboot> ping seska
PING seska (141.21.7.245) 56(84) bytes of data.
64 bytes from seska (141.21.7.245): icmp_seq=3 ttl=64 time=0.234 ms
64 bytes from seska (141.21.7.245): icmp_seq=7 ttl=64 time=0.230 ms
64 bytes from seska (141.21.7.245): icmp_seq=9 ttl=64 time=0.232 ms
64 bytes from seska (141.21.7.245): icmp_seq=13 ttl=64 time=0.232 ms
64 bytes from seska (141.21.7.245): icmp_seq=14 ttl=64 time=0.234 ms
64 bytes from seska (141.21.7.245): icmp_seq=15 ttl=64 time=0.232 ms
64 bytes from seska (141.21.7.245): icmp_seq=16 ttl=64 time=0.234 ms
64 bytes from seska (141.21.7.245): icmp_seq=18 ttl=64 time=0.228 ms
64 bytes from seska (141.21.7.245): icmp_seq=19 ttl=64 time=0.233 ms
64 bytes from seska (141.21.7.245): icmp_seq=20 ttl=64 time=0.246 ms
64 bytes from seska (141.21.7.245): icmp_seq=29 ttl=64 time=0.230 ms
64 bytes from seska (141.21.7.245): icmp_seq=33 ttl=64 time=0.228 ms
64 bytes from seska (141.21.7.245): icmp_seq=34 ttl=64 time=0.232 ms
64 bytes from seska (141.21.7.245): icmp_seq=37 ttl=64 time=0.230 ms
64 bytes from seska (141.21.7.245): icmp_seq=39 ttl=64 time=0.233 ms
64 bytes from seska (141.21.7.245): icmp_seq=40 ttl=64 time=0.232 ms
64 bytes from seska (141.21.7.245): icmp_seq=45 ttl=64 time=0.246 ms
64 bytes from seska (141.21.7.245): icmp_seq=47 ttl=64 time=0.230 ms
64 bytes from seska (141.21.7.245): icmp_seq=48 ttl=64 time=0.232 ms

--- seska ping statistics ---
48 packets transmitted, 19 received, 60% packet loss, time 47057ms
################

I have only two process, one is dummy and the second is the receive task,
which get activated when a packet received by the interrupt handler. I have
no any lwip TCP connection active. Just I activated my network.

As you have more experience with LWIP, you could point for experience about
increasing performance!

-Amir




reply via email to

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