Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1765670AbXHXVvV (ORCPT ); Fri, 24 Aug 2007 17:51:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760430AbXHXVvI (ORCPT ); Fri, 24 Aug 2007 17:51:08 -0400 Received: from e32.co.us.ibm.com ([32.97.110.150]:37572 "EHLO e32.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760243AbXHXVvG (ORCPT ); Fri, 24 Aug 2007 17:51:06 -0400 Date: Fri, 24 Aug 2007 16:51:03 -0500 To: David Miller Cc: dlstevens@us.ibm.com, tklein@de.ibm.com, themann@de.ibm.com, stefan.roscher@de.ibm.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, raisch@de.ibm.com, netdev-owner@vger.kernel.org, linuxppc-dev@ozlabs.org, akepner@sgi.com, meder@de.ibm.com, ossthema@de.ibm.com, shemminger@linux-foundation.org Subject: Re: RFC: issues concerning the next NAPI interface Message-ID: <20070824215103.GO4282@austin.ibm.com> References: <20070824085203.42f4305c@freepuppy.rosehill.hemminger.net> <20070824.144436.59664160.davem@davemloft.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070824.144436.59664160.davem@davemloft.net> User-Agent: Mutt/1.5.11 From: linas@austin.ibm.com (Linas Vepstas) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 750 Lines: 20 On Fri, Aug 24, 2007 at 02:44:36PM -0700, David Miller wrote: > From: David Stevens > Date: Fri, 24 Aug 2007 09:50:58 -0700 > > > Problem is if it increases rapidly, you may drop packets > > before you notice that the ring is full in the current estimated > > interval. > > This is one of many reasons why hardware interrupt mitigation > is really needed for this. When turning off interrupts, don't turn them *all* off. Leave the queue-full interrupt always on. --linas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/