netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Chapman <jchapman@katalix.com>
To: John Sigler <linux.kernel@free.fr>
Cc: netdev@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: 82557/8/9 Ethernet Pro 100 interrupt mitigation support
Date: Mon, 03 Sep 2007 14:33:35 +0100	[thread overview]
Message-ID: <46DC0D2F.2040902@katalix.com> (raw)
In-Reply-To: <46DBE393.30300@free.fr>

John Sigler wrote:
> 
> Hello everyone,
> 
> I have several systems with three integrated Intel 82559 (I *think*).
> 
> Does someone know if these boards support hardware interrupt mitigation?

82558/9 hardware does, sort of. But the e100 driver doesn't use it 
because it uses NAPI to minimize rx & tx interrupts.

> I.e. is it possible to configure them to raise an IRQ only if their
> hardware buffer is full OR if some given time (say 1 ms) has passed and
> packets are available in their hardware buffer.
> 
> I've been using the eepro100 driver up to now, but I'm about to try the
> e100 driver. Would I have to use NAPI? Or is this an orthogonal feature?

Use NAPI. The e100 driver has been NAPI-only for a while.

-- 
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development



  parent reply	other threads:[~2007-09-03 13:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-03 10:36 82557/8/9 Ethernet Pro 100 interrupt mitigation support John Sigler
2007-09-03 13:09 ` John Sigler
2007-09-03 13:33 ` James Chapman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-03 10:33 Marc Sigler
2007-09-04 15:56 ` Kok, Auke
2007-09-04 16:12   ` Brandeburg, Jesse
2007-09-04 16:41     ` John Sigler
2007-09-04 20:32       ` Brandeburg, Jesse

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=46DC0D2F.2040902@katalix.com \
    --to=jchapman@katalix.com \
    --cc=linux-net@vger.kernel.org \
    --cc=linux.kernel@free.fr \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).