netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Olsson <Robert.Olsson@data.slu.se>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: netdev@oss.sgi.com
Subject: [Fwd: [E1000] NAPI re-insertion w/ changes]
Date: Sat, 22 Mar 2003 16:34:01 +0100	[thread overview]
Message-ID: <15996.33385.784192.430037@robur.slu.se> (raw)
In-Reply-To: <3E7B25AC.5030604@pobox.com>



Jeff Garzik writes:
 > For review by the list... The other e100/e1000 changes are in the 2.5 

 > +#ifdef CONFIG_E1000_NAPI
 > +	/* Don't disable interrupts - rely on h/w interrupt
 > +	 * moderation to keep interrupts low.  netif_rx_schedule
 > +	 * is NOP if already polling. */
 > +	netif_rx_schedule(netdev);
 > +#else


It's clean but I have some concerns...

I think this will add interrupts when resources are fully utilized.
In other words a decrease in top performance. I say "think" because I have 
no numbers. 

At GIGE rate we have ~1 k interrupts/sec using interrupt delay. (it depend 
of ring sizes etc). We are now seeing Linux boxes with ~10 GIGE interfaces. 
So any effects gets multiplied.

It makes the use zero latency RX complicated. We see Ethernet getting
used for "new" applications as SCSI, filesystems etc. In current e1000 
we just can set the desired interrupt delay and relax.

If/when PCI-X uses message signalled interrupts (MSI) we have this "un-
necessary" load over PCI too with bus arbitrations etc.


IMO believe your old plan having e1000 irq disable and with mitigation as 
default feels better but testing is needed.

Cheers.

						--ro

  reply	other threads:[~2003-03-22 15:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21 14:46 [Fwd: [E1000] NAPI re-insertion w/ changes] Jeff Garzik
2003-03-22 15:34 ` Robert Olsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-22 18:47 Feldman, Scott
2003-03-22 20:28 ` Robert Olsson
2003-03-31 17:14 ` Robert Olsson
2003-03-27 16:54 Robert Olsson
2003-03-27 17:10 ` Jason Lunz
2003-03-28  8:27   ` Robert Olsson
2003-03-28 17:32     ` Jason Lunz
2003-03-28 18:43       ` Robert Olsson
2003-04-01 17:47 Feldman, Scott
2003-04-01 18:57 ` Robert Olsson
2003-04-01 21:16 ` Jeff Garzik
2003-04-01 19:13 Feldman, Scott
2003-04-01 19:23 ` Jason Lunz
2003-04-01 22:40   ` Jason Lunz
2003-04-01 19:44 ` Robert Olsson
2003-04-01 21:22 Feldman, Scott
2003-04-02  0:13 Feldman, Scott
2003-04-02  4:19 ` Jason Lunz

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=15996.33385.784192.430037@robur.slu.se \
    --to=robert.olsson@data.slu.se \
    --cc=jgarzik@pobox.com \
    --cc=netdev@oss.sgi.com \
    /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).