From: Armin Kuster <akuster@mvista.com>
To: John Cagle <jcagle@kernel.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 405GP network receive problem
Date: Fri, 29 Jun 2001 11:57:37 -0700 [thread overview]
Message-ID: <3B3CCFA1.C581A34F@mvista.com> (raw)
In-Reply-To: 20010629104618.A22541@kernel.org
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
John Cagle wrote:
>
> I am debugging a custom board design based on the 405GP and have a problem
> receiving lots of TCP/IP traffic (like FTP). We're using a 2.4 kernel based
> on Monta Vista's CDK 1.2. UDP traffic (like TFTP) works very well, but it
> doesn't ever have back-to-back receives, typically. The problem occurs
> at both 10mbit and 100Mbit.
>
> I have narrowed the problem down (using ttcp) to the following:
>
> During back-to-back receives (within microseconds) of two large (1500 bytes)
> TCP packets, the second packet is usually dropped by the 405GP. When I
> check ifconfig statistics, it shows the 1 lost packet, but also shows 2
> framing errors.
>
> Has anyone else seen this type of problem with the 405GP or does anyone
> know what the problem might be?
>
> Thanks,
> John
John,
the ethernet driver in hhl 1.2 had only one tx & rx buffer and we where
not flushing the cache properly. I have included the latest driver &
header file.
regards,
armin
[-- Attachment #2: 405_enet_latest.tar.gz --]
[-- Type: application/octet-stream, Size: 13069 bytes --]
next prev parent reply other threads:[~2001-06-29 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-27 12:43 Proper way to flush caches Justin (Gus) Hurwitz
2001-06-29 17:46 ` 405GP network receive problem John Cagle
2001-06-29 18:57 ` Armin Kuster [this message]
2001-07-04 18:52 ` Raymond Lo
-- strict thread matches above, loose matches on Subject: below --
2001-07-04 20:31 Marti, Felix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B3CCFA1.C581A34F@mvista.com \
--to=akuster@mvista.com \
--cc=jcagle@kernel.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.