All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Anders Linden <anli@perceptive.se>, linux-kernel@vger.kernel.org
Subject: Re: Network card timeouts
Date: Mon, 26 Nov 2001 15:32:16 -0500	[thread overview]
Message-ID: <3C02A6D0.58AE0FEE@mandrakesoft.com> (raw)
In-Reply-To: <E168SKg-0006jd-00@the-village.bc.nu>

Alan Cox wrote:
> 
> > The later card, Davicom, is probably not a well-known card, but
> > nevertheless, it works like shit in Linux. I am using Redhat 7.1 and th=
> > e
> > kernel 2.4.2-2. If I send more than 10M to such a card in an interval o=
> 
> Davicom is a bad tulip clone. It has a (not very good) davicom provided
> driver in 2.4.2 or you can use tulip or the updated davicom provided dfme
> driver in newer 2.4

tulip should work better IMHO for all davicom tulip clones -except- the
older ones which require doing a software crc for each packet.  For
those, the performance penalty is too high to integrate into the
mainline tulip driver.  So my advice is usually "try tulip, then
fallback to dmfe if software crc is required"

-- 
Jeff Garzik      | Only so many songs can be sung
Building 1024    | with two lips, two lungs, and one tongue.
MandrakeSoft     |         - nomeansno


      reply	other threads:[~2001-11-26 20:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21 18:16 Network card timeouts Anders Linden
2001-11-21 20:48 ` Joseph Fannin
2001-11-21 23:24   ` Jeff Garzik
2001-11-22 13:12 ` Tobias Ringstrom
2001-11-26 20:26 ` Alan Cox
2001-11-26 20:32   ` Jeff Garzik [this message]

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=3C02A6D0.58AE0FEE@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=anli@perceptive.se \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.