public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: David Sperry <dave_sperry@ieee.org>
Cc: "'dave_sperry@ieee.org'" <dasperry@comcast.net>,
	linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Poor UDP performance using 2.6.21-rc5-rt5
Date: Tue, 3 Apr 2007 08:43:04 +0200	[thread overview]
Message-ID: <20070403064304.GA17938@elte.hu> (raw)
In-Reply-To: <001d01c77584$6a92ffe0$7901a8c0@dad>


* David Sperry <dave_sperry@ieee.org> wrote:

> > > I think there is some kind of bad behavior happening in the Nvidia 
> > > driver with respect to softirq-net-tx and IRQ-8406.
> > 
> > yes. Part of the problem is that the forcedeth.c driver does not 
> > fully support NAPI - today i've implemented those bits (see them 
> > below), based on your testcase. The other part is that the Intel NIC 
> > uses MSI, while foredeth uses fasteoi, correct? [you can see this in 
> > /proc/interrupts]
> 
> In my case forcedeth seems to be picking up MSI for eth2 & eth3

> Could this be part of my problem?

i dont think it should be a problem.

	Ingo

  reply	other threads:[~2007-04-03  6:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-02 17:50 Poor UDP performance using 2.6.21-rc5-rt5 dave_sperry@ieee.org
2007-04-02 19:04 ` Ingo Molnar
2007-04-03  0:09   ` David Sperry
2007-04-03  6:43     ` Ingo Molnar [this message]
2007-04-03  8:51     ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2007-04-02 17:17 dave_sperry@ieee.org
2007-04-02 14:09 dave_sperry@ieee.org
2007-04-02 14:23 ` Ingo Molnar
2007-04-01 19:15 Dave Sperry
2007-04-01 20:07 ` Nivedita Singhvi
2007-04-01 22:00   ` Dave Sperry
2007-04-02  5:55   ` Ingo Molnar
2007-04-02  6:30     ` Ingo Molnar
2007-04-02  7:21 ` Ingo Molnar
2007-04-02  8:17   ` Dave Sperry
2007-04-02  9:37     ` Ingo Molnar

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=20070403064304.GA17938@elte.hu \
    --to=mingo@elte.hu \
    --cc=dasperry@comcast.net \
    --cc=dave_sperry@ieee.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@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