This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: problem with ethertap
- From: Bart Veer <bartv at ecoscentric dot com>
- To: mirkomassi at tiscali dot it
- Cc: ecos-discuss at sourceware dot org, gerardo dot rossi at studenti dot univr dot it
- Date: Sun, 20 Nov 2005 16:56:31 +0000 (GMT)
- Subject: Re: [ECOS] problem with ethertap
- References: <43745BEE00020DCF@mail-1.mail.tiscali.sys>
>>>>> "mirkomassi" == mirkomassi <mirkomassi@tiscali.it> writes:
> I have a problem with ethertap!... I have an application on
> eCos that transmit a lot of packets, packet size 1012 bytes, and
> i have an application on Linux that must receive these packages,
> but if the number of packets that transmit for example is ten,
> application on linux receive one packet only, and if the
> transmit is in loop, i don't receive null.
Is this traffic TCP or UDP? If TCP then ordinary TCP/IP windowing
should take care of flow control and nothing should get lost. If UDP
then that is inherently an unreliable protocol and packets may be
discarded on either the eCos side or the Linux side whenever they are
inconvenient. However normally there is enough buffering capacity in
various places to avoid problems.
First you will have to figure out where the packets are being lost:
inside eCos, by the synthetic target, or inside Linux. A good step
would be to enable ethernet traffic logging in the synthetic target.
If the packets never reach the host-side I/O auxiliary then the
problem must be on the eCos side and you may have to configure the
TCP/IP stack with more buffer space. If the packets do reach the
host-side then further investigation will be needed.
Bart
--
Bart Veer eCos Configuration Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss