public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: linux-kernel@vger.kernel.org
Subject: Re: Repeatable 2.4.0-test13-pre4 nfsd Oops rears it head again
Date: Sat, 30 Dec 2000 21:42:10 +1100	[thread overview]
Message-ID: <3A4DBC02.92C0FD9A@uow.edu.au> (raw)
In-Reply-To: <20001228161126.A982@lingas.basement.bogus> <200012282159.NAA00929@pizda.ninka.net> <20001228212116.A968@lingas.basement.bogus> <92ha5l$1qh$1@penguin.transmeta.com>

Linus Torvalds wrote:
> 
> I bet that others will have other recommendations, but so far I have at
> least personally had good luck with the eepro100.

The 3c905C is a well manufactured and very feature-rich NIC which at
present appears to have fewer problem reports than eepro100, 8139 or tulip.

Available in PCI, Cardbus, Mini-PCI.  A dual-interface PCI version has
just been released (3c982), although we've yet to hear of anyone trying
it with Linux.

3com provide full specs without any NDA restrictions, plus a GPL'ed
driver.

Perhaps most significantly, the 905 has full scatter/gather support.
This isn't used at present, but Alexey's zerocopy-sendfile patches
do utilise it.  He currently has scatter-gather support for acenic,
3c905 and sunhme.  I don't know what the plans are to support other
100 mbps NICs.

The in-kernel 3c59x.c isn't the world's fastest driver.  On the todo list
for 2.5 is MMIO support, scatter-gather maintenance, optional use of DPD
polling and implementation of the onboard multicast hash filter. And 
implementation of the on-board VLAN support if 2.5 becomes VLAN-capable.

-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-12-30 11:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-28 22:11 Repeatable 2.4.0-test13-pre4 nfsd Oops rears it head again Mike Elmore
2000-12-28 21:59 ` David S. Miller
2000-12-29  3:21   ` Mike Elmore
2000-12-29  3:47     ` Chris Wedgwood
2000-12-29  6:15     ` Linus Torvalds
2000-12-29 10:25       ` Chris Wedgwood
2000-12-30 10:42       ` Andrew Morton [this message]
2000-12-30 18:06         ` Francois Romieu
2000-12-30 23:01         ` NIC recommendations (was Re: Repeatable 2.4.0-test13-pre4...) Barry K. Nathan
2001-01-01 23:51           ` H. Peter Anvin
2000-12-29  8:14     ` Repeatable 2.4.0-test13-pre4 nfsd Oops rears it head again David Ford
  -- strict thread matches above, loose matches on Subject: below --
2000-12-29  8:51 Ray Strode
2000-12-29 16:15 Jeff Chua

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=3A4DBC02.92C0FD9A@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    /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