From owner-freebsd-net@FreeBSD.ORG Wed Jul 16 23:58:20 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4D9C7D6A for ; Wed, 16 Jul 2014 23:58:20 +0000 (UTC) Received: from smtp.rlwinm.de (smtp.rlwinm.de [IPv6:2a01:4f8:201:31ef::e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1283322AF for ; Wed, 16 Jul 2014 23:58:20 +0000 (UTC) Received: from hexe.rlwinm.de (p50834048.dip0.t-ipconnect.de [80.131.64.72]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.rlwinm.de (Postfix) with ESMTPSA id C2E00C0F3 for ; Thu, 17 Jul 2014 01:58:15 +0200 (CEST) Message-ID: <53C71196.4030501@rlwinm.de> Date: Thu, 17 Jul 2014 01:58:14 +0200 From: Jan Bramkamp User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: netmap, selective processing. References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: Wed, 16 Jul 2014 23:58:20 -0000 On 16.07.2014 19:48, Daniel Corbe wrote:> > I hope this it the right place to ask questions about netmap. I'm > toying with the idea of writing a netmap-based OSPF implementation > because bird's OSPF implementation isn't as good as its BGP > implementation, quagga doesn't scale well and openospfd doesn't compile > on 10-RELEASE or CURRENT. How many prefixes do you have in your OSPF area 0? If you run into scalability problems with OSPF on current x86 CPUs your network design probably is the cause of the problem e.g. redistributing announcements from BGP into OSPF. OSPF is just one more (rather ugly) IP protocol. Is moving the OSPF packets between kernel and userspace really a problem worth optimizing for? Putting netmap between the NIC and the kernel IP stack introduces overhead to all non OSPF packets unless your netmap application also implements IP routing and bypasses the kernel.