mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ion Badulescu <ionut@cs.columbia.edu>
To: Florian Weimer <Weimer@CERT.Uni-Stuttgart.DE>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NIC with polling support
Date: Tue, 31 Dec 2002 13:00:38 -0500	[thread overview]
Message-ID: <200212311800.gBVI0cM15151@buggy.badula.org> (raw)
In-Reply-To: <87el7yrvso.fsf@Login.CERT.Uni-Stuttgart.DE>

On Tue, 31 Dec 2002 17:35:19 +0100, Florian Weimer <Weimer@cert.uni-stuttgart.de> wrote:
> Dear all,
> 
> I guess I'm severe need of a 100BaseTX NIC with polling support in the
> driver.
> 
> A special application requires processing of 40,000 packets/second or
> more, and the interrupt load currently kills the machine (i.e. no
> scheduling during peak load).
> 
> Any suggestions which card I should use?  The driver has to be open
> source, and the card shouldn't be too expensive (i.e. in the usual
> price range of brand 100BaseTX NICs).

As far as I can tell, no driver in 2.4 supports NAPI (aka polling support)
with the exception of the tg3 driver -- but that's a GigE card.

The Adapter DuraLAN/Starfire driver (which I maintain) has been modified to
support NAPI, but those changes have not yet been included in the official
kernel. I can mail you the patch, if you want to give it a try. The cards
are on the expensive side, but not overly so (about $100/port).

Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
            than to open it and remove all doubt.

  reply	other threads:[~2002-12-31 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-31 16:35 Florian Weimer
2002-12-31 18:00 ` Ion Badulescu [this message]
2002-12-31 19:07 ` Jason Lunz
2003-01-01  0:27   ` Florian Weimer
2003-01-01  0:34   ` Florian Weimer

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=200212311800.gBVI0cM15151@buggy.badula.org \
    --to=ionut@cs.columbia.edu \
    --cc=Weimer@CERT.Uni-Stuttgart.DE \
    --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

all inboxes | Powered by JetHome®