lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1172558533.11949.38.camel@localhost.localdomain>
Date:	Tue, 27 Feb 2007 07:42:13 +0100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Jan-Bernd Themann <ossthema@...ibm.com>
Cc:	netdev <netdev@...r.kernel.org>, Thomas Klein <tklein@...ibm.com>,
	Jan-Bernd Themann <themann@...ibm.com>,
	Roland Dreier <rdreier@...co.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-ppc <linuxppc-dev@...abs.org>,
	Christoph Raisch <raisch@...ibm.com>,
	Marcus Eder <meder@...ibm.com>,
	Stefan Roscher <stefan.roscher@...ibm.com>
Subject: Re: [PATCH] ehea: NAPI multi queue TX/RX path for SMP

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 netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ