From owner-freebsd-net@FreeBSD.ORG Wed Feb 2 05:49:30 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5DBA1065672 for ; Wed, 2 Feb 2011 05:49:30 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6C64D8FC0C for ; Wed, 2 Feb 2011 05:49:29 +0000 (UTC) Received: by qyk36 with SMTP id 36so7344675qyk.13 for ; Tue, 01 Feb 2011 21:49:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=3p8/eekBdiSUJkMeDZxD7pdoQ9pbjbG3hdmtWposglM=; b=nUNDT1rY3ZDyJSlzLAsjJiL3+lLf34oJ4d0HvfohRa4gpcuPRN7ToR3D2jSipSxwl6 6PKQ/5G5iC0jCYbt/SzZJXEaIUn0NTytHXEYHfn/1/xrfq3G+MOEg1y1c5qpbW7UVYQH xQDdBJmVRp8pcXFJeU2DJ+uTJkcSoHCuxdmzc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=cAMubKoze3b8oKqvsLwZTtGCAgxl15EZUnXta/rMVjhvDEWQPzdrS+Ix8wzanYKCq6 +Vu4jh76yfkUl2JjTgg2hlCeam5O/+SeGFIDnKVGt0jC7zzzKN91HjlgEYrfG5qkunEc VfImTLPJirtFFr3D0YG/gmZgpVBvKShaYKx/o= MIME-Version: 1.0 Received: by 10.229.89.208 with SMTP id f16mr6092155qcm.43.1296625769237; Tue, 01 Feb 2011 21:49:29 -0800 (PST) Received: by 10.229.102.87 with HTTP; Tue, 1 Feb 2011 21:49:29 -0800 (PST) In-Reply-To: References: Date: Wed, 2 Feb 2011 08:49:29 +0300 Message-ID: From: Sergey Kandaurov To: Markus Oestreicher Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-net@freebsd.org" Subject: Re: Current state of FreeBSD routing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2011 05:49:30 -0000 On 2 February 2011 02:11, Markus Oestreicher wrote: > Hi there! > > After a few hours of reading list archives and source code I need some > clarification on the current state of FreeBSD forwarding capabilities. > > Given the following setup: > - Quad Core CPU > - Intel 82576 NIC (igb) > - 8.2-RELEASE > - Router with BGP full table > > 1) Queues: > Card and driver seem to have support for multiple TX/RX queues. > How many cores will it use for RX / TX per NIC? That depends on how many cpu cores you have. e.g. with several 82576 NICs installed I have 8 queues per each port. So it looks like # vmstat -ia | grep igb7 irq320: igb7:que 0 0 0 irq321: igb7:que 1 0 0 irq322: igb7:que 2 0 0 irq323: igb7:que 3 0 0 irq324: igb7:que 4 0 0 irq325: igb7:que 5 0 0 irq326: igb7:que 6 0 0 irq327: igb7:que 7 0 0 irq328: igb7:link 0 0 With Quad Core CPU you will have 4 queues. > > 2) Fastforwarding vs multiple netisr: > In the past (6.x) using fastforwarding=1 was the best option for dedicated routers. > I found "multiple netisr" added to 8.0. Can that help with routing on multiple cores? > Any experience from using it in production? > > 3) lagg: > I found lagg(4) mostly mentioned on home user setups. > Any experience with using lagg in high-pps environments? (>100k pps) > Will lagg play nicely together with multiple netisr routing or fastforwarding? > How much overhead will it add versus a single connection? > > Thanks a lot > > Markus -- wbr, pluknet