public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakob Oestergaard <jakob@unthought.net>
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: bdflush/rpciod high CPU utilization, profile does not make sense
Date: Tue, 12 Apr 2005 11:28:43 +0200	[thread overview]
Message-ID: <20050412092843.GB17359@unthought.net> (raw)
In-Reply-To: <1113267809.1956.242.camel@hole.melbourne.sgi.com>

On Tue, Apr 12, 2005 at 11:03:29AM +1000, Greg Banks wrote:
> On Tue, 2005-04-12 at 01:42, Jakob Oestergaard wrote:
> > Yes, as far as I know - the Broadcom Tigeon3 driver does not have the
> > option of enabling/disabling RX polling (if we agree that is what we're
> > talking about), but looking in tg3.c it seems that it *always*
> > unconditionally uses NAPI...
> 
> I've whined and moaned about this in the past, but for all its
> faults NAPI on tg3 doesn't lose packets.  It does cause a huge
> increase in irq cpu time on multiple fast CPUs.  What irq rate
> are you seeing?

Around 20.000 interrupts per second during the large write, on the IRQ
where eth0 is (this is not shared with anything else).

[sparrow:joe] $ cat /proc/interrupts
           CPU0       CPU1
...
169:    3853488  412570512   IO-APIC-level  eth0
...


But still, guys, it is the *same* server with tg3 that runs well with a
2.4 client but poorly with a 2.6 client.

Maybe I'm just staring myself blind at this, but I can't see how a
general problem on the server (such as packet loss, latency or whatever)
would cause no problems with a 2.4 client but major problems with a 2.6
client.

-- 

 / jakob


  reply	other threads:[~2005-04-12  9:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06 16:01 bdflush/rpciod high CPU utilization, profile does not make sense Jakob Oestergaard
2005-04-06 21:28 ` Trond Myklebust
2005-04-07 15:28   ` Jakob Oestergaard
2005-04-06 23:19 ` Greg Banks
2005-04-07 15:38   ` Jakob Oestergaard
2005-04-07 16:01     ` Greg Banks
2005-04-07 16:17     ` Trond Myklebust
2005-04-09 21:35       ` Jakob Oestergaard
2005-04-09 21:52         ` Trond Myklebust
2005-04-11  7:48           ` Jakob Oestergaard
2005-04-11 12:35             ` Trond Myklebust
2005-04-11 13:47               ` Jakob Oestergaard
2005-04-11 14:35                 ` Trond Myklebust
2005-04-11 14:41                   ` Jakob Oestergaard
2005-04-11 15:21                     ` Trond Myklebust
2005-04-11 15:42                       ` Jakob Oestergaard
2005-04-12  1:03                         ` Greg Banks
2005-04-12  9:28                           ` Jakob Oestergaard [this message]
2005-04-19 19:45                             ` Jakob Oestergaard
2005-04-19 22:46                               ` Trond Myklebust
2005-04-20 13:57                                 ` Jakob Oestergaard
2005-04-24  7:15                                   ` Jakob Oestergaard
2005-04-25  3:09                                     ` Trond Myklebust
2005-04-25 13:50                                       ` Jakob Oestergaard

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=20050412092843.GB17359@unthought.net \
    --to=jakob@unthought.net \
    --cc=gnb@melbourne.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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