st should now be almost read-only,
since it's very unlikely that anyone is making new ISA NE2000 and not
following the design rules.
Donald Becker [EMAIL PROTECTED]
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210
e driver first sets the
speed to 10baseT and checks for link beat. If it finds 10baseT link
beat it never tries 100baseTx.
The solution is to set the speed to 100baseTx using a driver option.
Read
http://www.scyld.com/network/vortex.html
The 3c595 is a very old card.
You will get better perf
On 12 Feb 2001, Jes Sorensen wrote:
> >>>>> "Donald" == Donald Becker <[EMAIL PROTECTED]> writes:
>
> Donald> On 9 Feb 2001, Jes Sorensen wrote:
> >> The ia64 kernel has gotten mis aligned load support, but it's slow
> >> as a do
dev->last_rx = jiffies;
> - np->stats.rx_bytes += skb->len;
> np->stats.rx_packets++;
> }
Easier fix:
- np->stats.rx_bytes += skb->len;
+ np->stats.rx
t. In some
cases the driver does basic polling to check for duplex changes, but
the semantics are not as clean as you would expect.
Donald Becker [EMAIL PROTECTED]
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Seco
lip.c driver at
http://www.scyld.com/network/tulip.html
for a driver with the many updates needed to support recent chips and
boards.
Donald Becker [EMAIL PROTECTED]
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Se
g transmit interrupts.
The better solution, which I've been adding to the drivers, is to check
again for a just-cleared Tx queue after setting tx_full.
That trades an extra comparison on a rarely followed path for a spinlock
that is taken for every transmit and interrupt.
Remember: spinlocks
43
chip, which has at least 70 different driver-visible board design
variations.)
Bottom line: Yes, it's redundant. But there was a reason.
Donald Becker [EMAIL PROTECTED]
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210
card is in
the "legacy" category, so it's better to make minimal change needed to
correct the obvious potential problem.
Donald Becker [EMAIL PROTECTED]
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Se
.
Media selection code is the most time consuming and error prone code in many
drivers. I would have avoiding doing that work if there had been an easy
answer.
Donald Becker [EMAIL PROTECTED]
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave.
On Sun, 3 Dec 2000, Chris Wedgwood wrote:
> On Sat, Dec 02, 2000 at 11:09:35AM -0500, Donald Becker wrote:
>
> Hey, I'll make it easy. Find an approach that fully handles only the Tulip
> and 3c59x drivers, and that is consistent.
>
> Actually, I starteed wor
driver will share IRQs.
The 'ne' driver will work for PCI cards, but is intended for ISA cards. It
will not share the IRQ.
Documentation for the ne2k-pci driver is at
http://www.scyld.com/network/ne2k-pci.html
> 1) ACPI
> 2) ISDN (Windbond - HiSax)
> 3) RealTek PCI NE2000 ether
useful.
The only significant advantage of interrupt mitigation is cache locality
when allocating new skbuffs, and having an additional mechanism to drop
packets under overwhelming load.
The disadvantage of Rx interrupt mitigation is adding latency just where it
might matter the most. Remember th
e transfers were slow
and not bursting.
Also note: it is possible to drop an Rx packet after the early Rx
interrupt.
Donald Becker [EMAIL PROTECTED]
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Beowulf-II Cluster Dist
, especially with evidence of
continued, willful violations.
Donald Becker [EMAIL PROTECTED]
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Second Generation Beowulf Clusters
Annapolis MD 21403 410-99
get it past Linus) then
> please feel free to do so - I'll be glad to cross it off my list sooner
> as opposed to later.
If the ne* drivers are going to be updated, you might want to add in the
full-duplex support of the latest ne2k-pci.c driver at
ftp://www.scyld.com/pub/net
to notice that
>and enable (or disable) advanced features. To blindly assume is just a
>PCI bus lockup waiting to happen...
Just in case you didn't catch it: this is not a PCI v2.0 vs. v2.1 issue.
The older Tulips work great with PCI v2.0 and v2.1. The bug is with longer
bursts a
s is a 386/486 PCI system, setting cache "
"alignment to %x.\n", dev->name,
0x01A0 | (x86 <= 4 ? 0x4800 : 0x8000));
I removed this code and replaced with the ability to set the variable "csr0"
as a module option. The
hernet? Have you looked at gigabit autonegotiation?
If you are proposing a new interface (and obviously tossing the
existing MII-MDIO emulation that has existed for a few years) you should at
least support current hardware.
Donald Becker [EMAIL PROTECTED]
Scyld Computing Corporati
ce was not released, requiring a reboot between each
driver test. Trivial fix.
The MII read code is no longer reliable. I spent twenty minutes at
the show, but couldn't figure out the problem. I haven't been able
reproduce the problem locally with my 2.2 code and someone old
On Thu, 8 Feb 2001, Ion Badulescu wrote:
> On Thu, 8 Feb 2001, Donald Becker wrote:
>
> > > > The align-copy should *never* be required because the alignment differs
> > > > between DIX and E-II encapsulated packets. The machine shouldn't crash
> >
On 9 Feb 2001, Jes Sorensen wrote:
> >>>>> "Jeff" == Jeff Garzik <[EMAIL PROTECTED]> writes:
> Jeff> Donald Becker wrote:
> >> On Tue, 16 Jan 2001, Jeff Garzik wrote: > * IA64 support (Jes) Oh,
> >> and this is completely bogus. This
ng the interrupt count in /proc/interrupts.
Try booting the kernel with "noapic", which we recommend as the safe
default setting.
Donald Becker [EMAIL PROTECTED]
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210
p I'm using is the DEC 21143, which means that we skip over the two
> conditional blocks, so the first thing that happens when we call this is to
> wait around doing nothing for a millisecond. Is there some subtle
> reason why we would want to wait around for a millisecond before
24 matches
Mail list logo
