All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Olsson <Robert.Olsson@data.slu.se>
To: Steffen Persvold <sp@scali.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"David S. Miller" <davem@redhat.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: NAPI and tg3
Date: Tue, 7 Jan 2003 19:51:27 +0100	[thread overview]
Message-ID: <15899.8623.323398.889764@robur.slu.se> (raw)
In-Reply-To: <Pine.LNX.4.44.0301070015320.16633-100000@sp-laptop.isdn.scali.no>


Steffen Persvold writes:
 > 
 > I've also tried the NAPI patch for e1000 and it experience the same 
 > performance problem with multithreaded apps. The "NAPI-HOWTO" doesn't 
 > mention that this could be an issue at all. Does any of the NAPI authors 
 > (Jeff ?) have any comments ?

 Well wasn't ksoftirqd the general solution to schedule softirq's to run
 before next interrupt and by putting them under scheduler control the
 consecutive softirq's is prevented to monopolize the CPU.

 Well you're right the doc may mention this...

 Cheers.
						--ro

  reply	other threads:[~2003-01-07 18:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-04 15:23 NAPI and tg3 Steffen Persvold
2003-01-06 15:00 ` Steffen Persvold
2003-01-06 16:36   ` Alan Cox
2003-01-06 16:12     ` Steffen Persvold
2003-01-06 17:58       ` Alan Cox
2003-01-07 15:24         ` Steffen Persvold
2003-01-07 18:51           ` Robert Olsson [this message]
2003-01-07 20:54             ` Steffen Persvold
  -- strict thread matches above, loose matches on Subject: below --
2003-01-07 22:21 Robert Olsson
2003-01-08  0:07 ` Steffen Persvold
2003-01-09 17:21   ` Robert Olsson
2003-01-10  9:00     ` David S. Miller

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=15899.8623.323398.889764@robur.slu.se \
    --to=robert.olsson@data.slu.se \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sp@scali.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 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.