[ECOS] Network code unstable (Solved).

[Pieter Truter]

I think the problem appears when the network is at a lower priority than the
user thread. It will only appear if the network is flooded (ie. download of
big file). The network stack never times out or recover from it. Small
batches of work seems fine.

I run some test for you. It fails on priority <= 10, 11 and up is fine.

I hope this helps.

 
-----Original Message-----
From: Gary Thomas [mailto:gthomas@redhat.com]
Sent: Tuesday, February 12, 2002 11:16 AM
To: Pieter Truter
Cc: eCos Disuss
Subject: RE: [ECOS] Network code unstable (Solved).


On Tue, 2002-02-12 at 11:51, Pieter Truter wrote:
> 
> I played around with my thread priority and made it 15 instead of 10. That
> solved my problem.
> 

Is this [broken] testcase something you can share with me?  I'd like to 
understand the problems so we can fix them or document how to avoid them
like you have.

> For the record what should thead priorities be, not to interfere with the
> network?
> 
> Thanks
> 
> -----Original Message-----
> From: Andrew Lunn [mailto:andrew.lunn@ascom.ch]
> Sent: Tuesday, February 12, 2002 10:33 AM
> To: Pieter Truter
> Cc: eCos Disuss
> Subject: Re: [ECOS] Network code unstable.
> 
> 
> On Tue, Feb 12, 2002 at 10:27:47AM -0800, Pieter Truter wrote:
> > This is only when I download big files (250Kb and up)
> 
> The TFTP server has two different retry counters. For each 512byte
> packet it allows a number of retires and then gives up. Also, there is
> a maximum for the whole transfer. If you exceed either of these it
> closes the connection.
> 
> Check for this. Maybe you are loosing packets or have a bad link?
> 
>       Andrew
> 
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss


Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss