From owner-freebsd-ipfw Tue Nov 19 2:59: 8 2002 Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC64537B401 for ; Tue, 19 Nov 2002 02:59:07 -0800 (PST) Received: from fump.kawo2.rwth-aachen.de (fump.kawo2.RWTH-Aachen.DE [134.130.181.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id 505E343E4A for ; Tue, 19 Nov 2002 02:59:06 -0800 (PST) (envelope-from alex@fump.kawo2.rwth-aachen.de) Received: from fump.kawo2.rwth-aachen.de (localhost [127.0.0.1]) by fump.kawo2.rwth-aachen.de (8.12.5/8.12.5) with ESMTP id gAJAx4JA011032 for ; Tue, 19 Nov 2002 11:59:04 +0100 (CET) (envelope-from alex@fump.kawo2.rwth-aachen.de) Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.12.5/8.12.5/Submit) id gAJAx465011031 for freebsd-ipfw@FreeBSD.org; Tue, 19 Nov 2002 11:59:04 +0100 (CET) Date: Tue, 19 Nov 2002 11:59:04 +0100 From: Alexander Langer To: freebsd-ipfw@FreeBSD.org Subject: ipfw2 on SMP Message-ID: <20021119105904.GK4666@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. User-Agent: Mutt/1.5.1i Sender: owner-freebsd-ipfw@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG HI! Does ipfw2 (box does use DEVICE_POLLING) on -CURRENT benefit from 2 CPUs? We have quite the same incoming / outgoing traffic here, but I don't know the actual design of ipfw2 or the bridging-code, so I wondered if that would benefit from a 2nd CPU, or if the CPUs lock theirselves to the inefficiency. Comments? Stats? Already doing this somewhere? :) Thanks Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message