From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yinghai Lu Subject: Re: [PATCH] forcedeth: make msi-x different name for rx-tx Date: Fri, 06 Feb 2009 09:54:32 -0800 Message-ID: <498C7958.4010109@kernel.org> References: <498BC3A8.9040203@kernel.org> <20090206144948.GD18368@elte.hu> <498C6C15.3050807@kernel.org> <20090206171544.GA16190@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jeff Garzik , Andrew Morton , Ayaz Abdulla , "David S. Miller" , "linux-kernel@vger.kernel.org" , NetDev To: Ingo Molnar Return-path: Received: from hera.kernel.org ([140.211.167.34]:40732 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757557AbZBFRz2 (ORCPT ); Fri, 6 Feb 2009 12:55:28 -0500 In-Reply-To: <20090206171544.GA16190@elte.hu> Sender: netdev-owner@vger.kernel.org List-ID: Ingo Molnar wrote: > * Yinghai Lu 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). YH