RE: [lwip-users] Regarding Packet Loss in UDP mode - LwIP TCP/IP stack

[Matthew Yingling]

Revathy,

Try running your PC and board at half-duplex.  Some PCs will send out rather
bursty data streams, and half-duplex instead of full-duplex can help slow
this down.  When you put sleep() statements in your PC code, you are forcing
a somewhat smoother flow out of your PC network card.  If your code does a
lot of processing, the interrupt code might be working better because it
does something everytime the ethernet hardware says data is available, and
not just when it feels like checking for data (after potentially overflowing
any hardware buffering).

Matthew

-----Original Message-----
From: address@hidden
[mailto:address@hidden Behalf Of
revathy
Sent: Wednesday, May 03, 2006 5:34 AM
To: Mailing list for lwIP users
Subject: RE: [lwip-users] Regarding Packet Loss in UDP mode - LwIP
TCP/IP stack


Hi Kieran,

1) If it is a queue problem how I need to approach the problem?

2) Also, one thing I wanted to tell at this time.
        We tried 2 set of patch related with LwIP stack, from Analog Devices 
site.
        a) One with Jan 2005 version (where the packets are received by means of
polling )
        b) The second one is of December 2005 version (where packets are 
received
through Interrupt)

The second one is better than the first.

Do have any suggestion based on this observation?

Revathy



-----Original Message-----
From: address@hidden
[mailto:address@hidden
Behalf Of Kieran Mansley
Sent: Wednesday, May 03, 2006 2:49 PM
To: Mailing list for lwIP users
Subject: RE: [lwip-users] Regarding Packet Loss in UDP mode - LwIP
TCP/IP stack


On Wed, 2006-05-03 at 14:42 +0530, revathy wrote:
> Hi Kieran,
>               Thanks a lot for trying to attempt my problem.
>
>       Yes, as you said in UDP mode, packet loss is common.
> But, I tried with less traffic situation, meaning PC to board alone
(static
> mode)
> and no switch in between (This is by using crossover cable).
>       In that case also packet loss is happening, if iam not using the
> sleep(100).
> what can I do?

Investigate where in the UDP/IP stack the packets are being dropped.
Most probably this is at the receiver, and most probably it's due to
some queue getting full.  I'm not sure where the queues are in the
receiver, but it should be a pretty quick job to look through and add
some sort of instrumentation at each queue whenever a packet is dropped.

Kieran



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

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

__________ NOD32 1.1427 (20060303) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com




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