From owner-freebsd-net@FreeBSD.ORG Wed Nov 21 02:30:25 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0FC0F6FB for ; Wed, 21 Nov 2012 02:30:25 +0000 (UTC) (envelope-from khatfield@socllc.net) Received: from smtp151.dfw.emailsrvr.com (smtp151.dfw.emailsrvr.com [67.192.241.151]) by mx1.freebsd.org (Postfix) with ESMTP id CBF5D8FC18 for ; Wed, 21 Nov 2012 02:30:24 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp5.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 2B3A058062; Tue, 20 Nov 2012 21:30:24 -0500 (EST) X-Virus-Scanned: OK Received: by smtp5.relay.dfw1a.emailsrvr.com (Authenticated sender: khatfield-AT-socllc.net) with ESMTPSA id 88C7B58099; Tue, 20 Nov 2012 21:30:23 -0500 (EST) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD boxes as a 'router'... References: <1353448328.76219.YahooMailClassic@web121602.mail.ne1.yahoo.com> <50AC08EC.8070107@mu.org> <832757660.33924.1353460119408@238ae4dab3b4454b88aea4d9f7c372c1.nuevasync.com> <250266404.35502.1353464214924@238ae4dab3b4454b88aea4d9f7c372c1.nuevasync.com> From: khatfield@socllc.net Mime-Version: 1.0 In-Reply-To: Message-Id: <1805311939.35859.1353465022550@238ae4dab3b4454b88aea4d9f7c372c1.nuevasync.com> Date: Tue, 20 Nov 2012 20:30:18 -0600 To: Adrian Chadd X-NS-Received: from Apple-iPhone5C2/1001.525(khatfield@socllc.net) SECURED(HTTPS); Wed, 21 Nov 2012 02:30:20 +0000 (UTC) Cc: Barney Cordoba , Jim Thompson , Alfred Perlstein , "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 21 Nov 2012 02:30:25 -0000 Thank you, I certainly will. On Nov 20, 2012, at 8:23 PM, "Adrian Chadd" wrote: > The next time you have a chance to do high PPS tests, please compile > in KTR and take a schedgraph trace or two. > > Read the schedgraph.py source in /usr/src/tools/ for a quick overview. > > It'd be nice to have a public record somewhere of this issue > diagnosed. It may have just been some of the really odd edge case > behaviour the intel 10GE NICs did (at least, before scottl and the > netflix team were let at it.) > > > > Adrian