Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-mips@oss.sgi.com, Ralf Baechle <ralf@oss.sgi.com>,
	marcelo@conectiva.com.br
Subject: Re: [2.4 PATCH] pcnet32.c - tx underflow error
Date: Wed, 10 Jul 2002 16:51:45 -0700	[thread overview]
Message-ID: <3D2CC891.1010506@mvista.com> (raw)
In-Reply-To: E17SRFB-00087H-00@the-village.bc.nu

Alan Cox wrote:

>>This patch fixes a tx underflow error for 79c973 chip.  It essentially delay 
>>the transmission until the whole packet is received into the on-chip sdram.
>>
>>The patch is already accepted by Marcelo for the 2.4 tree, I think.
>>
> 
> Which slows the stuff down for people with real computers.


Contrary to what it might appear at first glance, it does not really.

While it delays the start of a transmission of the first packet, the delay 
does not aggregate in a steam of data.  The bottle neck is either in upper 
layer (how fact upper layer generates packets) or in the link layer (when we 
exceed the maximum bandwitch of the wire, in which case we always have plenty 
of full packets to send).

The delay itself is small (should be < 100us typically).  So there is no 
impact on interactive packets.  Note if the delay is not small (e.g., on 
system where PCI bus arbitration may be broken), then you *will* have the tx 
underflow problem.

So on a good system the delay should be really small (especially if you 
compare to what it takes to transmit the whole packet to the other end).  On a 
bad system where the delay can be long, then you will need the fix anyway.

Jun

> Please apply
> some kind of heuristic to this - eg switch to delaying if you exceed
> 50 failures in a 60 second period.
> 
> Alan
> 

  parent reply	other threads:[~2002-07-10 23:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10 21:56 [2.4 PATCH] pcnet32.c - tx underflow error Jun Sun
2002-07-10 23:51 ` Alan Cox
2002-07-10 23:51   ` Alan Cox
2002-07-10 23:51   ` Jun Sun [this message]
2002-07-11  2:21     ` Alan Cox
2002-07-11  2:21       ` Alan Cox
2002-07-11  3:01     ` Jason Gunthorpe
2002-07-11  0:08   ` Jun Sun
2002-07-11  2:16     ` Alan Cox
2002-07-11  2:16       ` Alan Cox
2002-07-11  8:12       ` Thomas Bogendoerfer
2002-07-12  2:51   ` Marcelo Tosatti
2002-07-12  2:51     ` Marcelo Tosatti
2002-07-12 18:26     ` Jun Sun

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=3D2CC891.1010506@mvista.com \
    --to=jsun@mvista.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-mips@oss.sgi.com \
    --cc=marcelo@conectiva.com.br \
    --cc=ralf@oss.sgi.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