netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Krogh <jesper@krogh.cc>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Joe Korty <joe.korty@ccur.com>,
	Ayaz Abdulla <aabdulla@nvidia.com>
Subject: eth0: too many iterations (16) in nv_nic_irq.
Date: Sun, 05 Apr 2009 10:19:35 +0200	[thread overview]
Message-ID: <49D86997.6010304@krogh.cc> (raw)

I have a 2.6.29 kernel which fills up the "dmesg-buffer" with these:

eth0: too many iterations (16) in nv_nic_irq.

$ dmesg | grep -c "too many iterations"
1986

I have seen the commit below.. is the fix just to set the limit to 30 
instead? or is there a "real bug" underneath?

commit dccd547e2bf2c01a13c967ae03a705338394fad6
Author: Joe Korty <joe.korty@ccur.com>
Date:   Wed Oct 29 14:22:16 2008 -0700

     forcdeth: increase max_interrupt_work

     This eliminates the following often-generated warning from my 64 bit
     Opteron SMP test stand:

         eth0: too many iterations (6) in nv_nic_irq

     According to the web, the problem is that the forcedeth driver has a
     too-low value for max_interrupt_work.  Grepping the kernel I see that
     forcedeth has the second lowest value of all ethernet drivers (ie, 6).
     Most are in the 20-40 range.  So this patch increases this a bit, 
from 6
     to 15 (at 15 forcedeth becomes the driver with third-lowest
     max_interrupt_work value).

     My test stand, which used to print out the above warnings repetitively
     whenever it was under heavy net load, no longer does so.

     Signed-off-by: Joe Korty <joe.korty@ccur.com>
     Cc: Ayaz Abdulla <aabdulla@nvidia.com>
     Cc: Jeff Garzik <jeff@garzik.org>
     Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
     Signed-off-by: Jeff Garzik <jgarzik@redhat.com>

             reply	other threads:[~2009-04-05  8:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-05  8:19 Jesper Krogh [this message]
2009-04-06 14:25 ` eth0: too many iterations (16) in nv_nic_irq Joe Korty

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=49D86997.6010304@krogh.cc \
    --to=jesper@krogh.cc \
    --cc=aabdulla@nvidia.com \
    --cc=joe.korty@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).