Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932932AbXB0Gmb (ORCPT ); Tue, 27 Feb 2007 01:42:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932893AbXB0Gmb (ORCPT ); Tue, 27 Feb 2007 01:42:31 -0500 Received: from gate.crashing.org ([63.228.1.57]:52697 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932889AbXB0Gma (ORCPT ); Tue, 27 Feb 2007 01:42:30 -0500 Subject: Re: [PATCH] ehea: NAPI multi queue TX/RX path for SMP From: Benjamin Herrenschmidt To: Jan-Bernd Themann Cc: netdev , Thomas Klein , Jan-Bernd Themann , Roland Dreier , linux-kernel , linux-ppc , Christoph Raisch , Marcus Eder , Stefan Roscher In-Reply-To: <200702261700.51220.ossthema@de.ibm.com> References: <200702261700.51220.ossthema@de.ibm.com> Content-Type: text/plain Date: Tue, 27 Feb 2007 07:42:13 +0100 Message-Id: <1172558533.11949.38.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1088 Lines: 27 On Mon, 2007-02-26 at 17:00 +0100, Jan-Bernd Themann wrote: > Hi! > > This patch replaces the former posted patch > ([PATCH] ehea: Optional TX/RX path optimized for SMP) and provides > a functionality that allows parallel RX processing on multiple RX > queues by using dummy netdevices as proposed by Roland Dreier. > The fairness amongst this net devices and other network devices > is thus better than in our first approach. > > Is there a way to avoid overloading a single CPU with multiple netdev > receive processes using NAPI? A distribution based on CPU load might > help to improve the throughput. Pinning interrupts shows there is > still some room for improvements. You may also want to look at the patches proposed by Dave Miller for splitting NAPI from netdevice so you can actually instanciate multiple NAPI "pollers" Ben. - 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/