.\" Copyright (c) 1983, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
.\" %sccs.include.redist.man%
.\" @(#)ec.4 8.1 (Berkeley) %G%
.Nd 3Com 10 Mb/s Ethernet interface
.Cd "device ec0 at uba0 csr 161000 vector ecrint eccollide ecxint flags 0"
interface provides access to a 10 Mb/s Ethernet network through
The hardware has 32 kilobytes of dual-ported memory on the
is used for internal buffering by the board, and the interface code reads
the buffer contents directly through the
The address of this memory is given in the
in the configuration file.
The first interface normally has its memory at Unibus address 0.
Each of the host's network addresses
is specified at boot time with an
interface employs the address resolution protocol described in
to dynamically map between Internet and Ethernet addresses on the local
The interface normally tries to use a
to minimize copying data on input and output.
The use of trailers is negotiated with
This negotiation may be disabled, on a per-interface basis,
The interface software implements an exponential backoff algorithm
when notified of a collision on the cable. This algorithm utilizes
interval timer in calculating a series
of random backoff values. The algorithm is as follows:
Initialize the mask to be all 1's.
If the mask is zero, 16 retries have been made and we give
Shift the mask left one bit and formulate a backoff by
masking the interval timer with the smaller of the complement of this mask
and a 5-bit mask, resulting in a pseudo-random number between 0 and 31.
This produces the number of slot times to delay,
where a slot is 51 microseconds.
Use the value calculated in step 3 to delay before retransmitting
The delay is done in a software busy loop.
After 16 retransmissions using the
exponential backoff algorithm described above, the packet
.It ec%d: input error (offset=%d).
The hardware indicated an error
in reading a packet off the cable or an illegally sized packet.
The buffer offset value is printed for debugging purposes.
.It ec%d: can't handle af%d.
a message with addresses formatted in an unsuitable address
family; the packet was dropped.
The hardware is not capable of talking to itself. The software
implements local sending and broadcast by sending such packets to the
loop interface. This is a kludge.
Backoff delays are done in a software busy loop. This can degrade the
system if the network experiences frequent collisions.