Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 May 1999 23:49:05 +0100 (BST)
From:      Doug Rabson <dfr@nlsystems.com>
To:        Dennis <dennis@etinc.com>
Cc:        Wilko Bulte <wilko@yedi.iaf.nl>, hackers@freebsd.org
Subject:   Re: What is a "transmit underflow"?
Message-ID:  <Pine.BSF.4.05.9905102347190.447-100000@herring.nlsystems.com>
In-Reply-To: <199905102218.SAA11495@etinc.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 10 May 1999, Dennis wrote:

> In case some of you care, here is what it is. The proper term is
> "transmitter underrun", but that is not really important.
> 
> Once a frame has begun transmission (and this goes for HDLC and other
> continuous packet protocols as well), all of the bytes of the frame/packet
> must be in contiguous time slots until the complete end of frame has been
> sent. With a bus master, the board must be able to fetch the data from
> system memory in time to fill all the slots. If the device cannot get the
> bus (usually because some other device has it) in time to fill the slot,
> then the frame must be aborted and an underrun occurs. If you get a lot of
> these it basically means that  you are out of bus bandwidth or that some
> other device is hogging the bus. This is typically why you will start to
> lose packets, no matter how fast your CPU is, at some point where
> contention for the bus is too high. Since most devices give priority to the
> receiver, problems usually manifest themselves as transmitter underruns first.


I don't think this is the case with the tulip. I have one alpha machine
which exhibits the problem and it *always* happens on the first large nfs
write the machine makes. Nothing else in the machine is using the bus for
anything significant at the time.

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9905102347190.447-100000>