public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Nikolay Marusov <nmarusov@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] ea2468 Ethernet overrun
Date: Wed, 03 Jun 2009 13:55:00 -0000	[thread overview]
Message-ID: <20090603135544.GF27508@lunn.ch> (raw)
In-Reply-To: <5addeae60906030643h354a9c6dq8da568ead5c8c63@mail.gmail.com>

On Wed, Jun 03, 2009 at 05:43:04PM +0400, Nikolay Marusov wrote:
> Hello!
> 
> I am playing with Embedded Artists LPC2468-16 OEM Board.
> Has anybody encounetered with a problem of TX overrun while
> transmitting Ethernet packets?
> Device works pretty well at 10Mbit/s but regullarly drops packet when
> transmitting at 100Mbit/s.
> What may be the cause?

Is it an overrun or an underrun?

I've seen underrun problems before in an intel chipset. The problem
was that the DMA would start transferring the packet from the host RAM
to the ethernet chipset. When X bytes of the packet had arrived at the
ethernet, the ethernet started sending them on the wire. Under heavy
memory load, the DMA was slower than the Ethernet sending bytes on the
wire, and with long packets the ethernet chip would empty its buffer
and then throw an underrun error. I had the change the Ethernet
chipset to have a bigger X so it had more buffered bytes before it
started sending them to the wire.

        Andrew

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

  reply	other threads:[~2009-06-03 13:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03 13:43 Nikolay Marusov
2009-06-03 13:55 ` Andrew Lunn [this message]
2009-06-03 14:19   ` Nikolay Marusov

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=20090603135544.GF27508@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=nmarusov@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).