[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090209120057.GB17782@elte.hu>
Date: Mon, 9 Feb 2009 13:00:57 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Yinghai Lu <yinghai@...nel.org>
Cc: Jeff Garzik <jeff@...zik.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ayaz Abdulla <aabdulla@...dia.com>,
"David S. Miller" <davem@...emloft.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
NetDev <netdev@...r.kernel.org>
Subject: Re: [PATCH] forcedeth: make msi-x different name for rx-tx
* Yinghai Lu <yinghai@...nel.org> wrote:
> Ingo Molnar wrote:
> > * Yinghai Lu <yinghai@...nel.org> wrote:
> >
> >> Ingo Molnar wrote:
> >>> Cool cleanups!
> >>>
> >>> Would you mind to also fix the following - on all my systems that have
> >>> forcedeth gigabit ethernet i've been getting these bogus warnings for
> >>> _years_, under moderate load:
> >>>
> >>> eth2: too many iterations (16) in nv_nic_irq.
> >>>
> >>> I think a 64 iterations limit will work much better. (i tried a limit of 50
> >>> a year ago for a while and it worked fine and had no side effects - and the
> >>> bogus warnings were done.)
> >> you may enable CONFIG_FORCEDETH_NAPI.
> >>
> >> we should enable NAPI for forcedeth by default, and try to squash more bugs out.
> >
> > i do have that:
> >
> > CONFIG_FORCEDETH=y
> > CONFIG_FORCEDETH_NAPI=y
> >
> > and the messages still come.
>
> so you systems are using ioapic routing, or msi.
>
> and those messages are from
> nv_nic_irq_optimized or nv_nic_irq
> for TX or OTHER (timerirq).
yes, IO-APIC:
18: 81386 306713817 0 0 1413724087 0 0
0 0 0 0 0 0 0 0
0 IO-APIC-fasteoi eth2
Those messages do come and are annoying.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists