netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org
Cc: netdev@vger.kernel.org, joe.korty@ccur.com, aabdulla@nvidia.com
Subject: Re: [patch 5/7] forcdeth: increase max_interrupt_work
Date: Sun, 02 Nov 2008 08:30:54 -0500	[thread overview]
Message-ID: <490DAB8E.3030006@garzik.org> (raw)
In-Reply-To: <200810292122.m9TLMGAI020173@imap1.linux-foundation.org>

akpm@linux-foundation.org wrote:
> From: Joe Korty <joe.korty@ccur.com>
> 
> 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>
> ---
> 
>  drivers/net/forcedeth.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

applied



      reply	other threads:[~2008-11-02 13:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29 21:22 [patch 5/7] forcdeth: increase max_interrupt_work akpm
2008-11-02 13:30 ` Jeff Garzik [this message]

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=490DAB8E.3030006@garzik.org \
    --to=jeff@garzik.org \
    --cc=aabdulla@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=joe.korty@ccur.com \
    --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).