From: Francois Romieu <romieu@cogenit.fr>
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 19:06:36 +0100 [thread overview]
Message-ID: <20001230190636.A11235@se1.cogenit.fr> (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> <3A4DBC02.92C0FD9A@uow.edu.au>
In-Reply-To: <3A4DBC02.92C0FD9A@uow.edu.au>
Andrew Morton <andrewm@uow.edu.au> écrit :
[...]
> 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.
I guess that the lack of problem reports for the epic chipset comes from
a smaller user base. FWIW, I haven't experienced real problems with
it (observation base: 20~30 boards). Neither did I with the few 3c905 used btw.
[...]
> Perhaps most significantly, the 905 has full scatter/gather support.
May be done for the epic. TODO++
--
Ueimor
-
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/
next prev parent reply other threads:[~2000-12-30 18:37 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
2000-12-30 18:06 ` Francois Romieu [this message]
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=20001230190636.A11235@se1.cogenit.fr \
--to=romieu@cogenit.fr \
--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