From owner-freebsd-net@FreeBSD.ORG Sun Jul 27 17:50:47 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3500B4CA for ; Sun, 27 Jul 2014 17:50:47 +0000 (UTC) Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E772921D5 for ; Sun, 27 Jul 2014 17:50:46 +0000 (UTC) Received: by mail-qg0-f43.google.com with SMTP id a108so7445458qge.30 for ; Sun, 27 Jul 2014 10:50:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=yo22lp2BsYDX6+fvcmgvtKwiTkRPBSgMZjoKZXQDMpg=; b=jGt3PTq2rmwIRnrBm9Byx2PAM2YVRQaBUlINlIdOJQYzGXQRnPG6ACAnh50zW5LYdo pZknx52TGFpqK6C3r1djXMBuOOuSiElZaXPCFq3AzZ7s2CyALuwi/j+1dyWAjpgTSPhq etDB76xDjrCN7PLKVAdfDJg2XM8nqiEECWK/L6aj0RqDVovwnVnIfNeXtjZIdKktA7fR kePxrWtzwKylbUVm6InUDLv9YazfL5DUV/52WpQ/YgRrEgL5Jm0fJBPIZLQTfpnGYtmt dfAV9uuyQHAFMvzo352ssq8tGTKYbcOqJGjHRRy23gKu5jwZaA8dOD5Oy35PpNUqWg1F 2UcQ== MIME-Version: 1.0 X-Received: by 10.140.107.4 with SMTP id g4mr38326836qgf.100.1406483445883; Sun, 27 Jul 2014 10:50:45 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.1.6 with HTTP; Sun, 27 Jul 2014 10:50:45 -0700 (PDT) In-Reply-To: <53D4F77B.9020009@gmail.com> References: <53CE80DD.9090109@gmail.com> <53D4600A.1010505@gmail.com> <53D4F77B.9020009@gmail.com> Date: Sun, 27 Jul 2014 10:50:45 -0700 X-Google-Sender-Auth: hMEAHDsePMohKwLBZpK2lnaXjhI Message-ID: Subject: Re: fastforward/routing: a 3 million packet-per-second system? From: Adrian Chadd To: John Jasen Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jul 2014 17:50:47 -0000 Yeah, there's something odd going on. You shouldn't see any of that lock contention if flowtable is enabled. Thus I think there's Oh wait, the fastfwd code doesn't know about flowtables. I just looked at it (sys/netinet/ip_fastfwd.c.) Try disabling fastfwd for a test and see if the lock profile improves. (Set debug.lock.prof.reset=1 to clear the profiling data before you do it.) -a On 27 July 2014 05:58, John Jasen wrote: > I shouldn't even be coming close to maxflows in this test scenario. > > net.flowtable.enable: 1 > net.flowtable.maxflows: 1042468 > > On 07/26/2014 10:20 PM, Adrian Chadd wrote: >> Flowtable is enabled? That's odd, it shouldn't be showing up like that. >> >> >> >> -a >> >> >> >