From owner-freebsd-net@FreeBSD.ORG Fri Mar 16 22:55:05 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 7F1E81065672 for ; Fri, 16 Mar 2012 22:55:05 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 4070F8FC17 for ; Fri, 16 Mar 2012 22:55:05 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 5F1797300A; Sat, 17 Mar 2012 00:13:37 +0100 (CET) Date: Sat, 17 Mar 2012 00:13:37 +0100 From: Luigi Rizzo To: grarpamp Message-ID: <20120316231337.GA62350@onelab2.iet.unipi.it> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org Subject: Re: netmap 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: Fri, 16 Mar 2012 22:55:05 -0000 On Fri, Mar 16, 2012 at 06:48:48PM -0400, grarpamp wrote: > Hi. I read most of the netmap paper. In short, cool work :) > > I have one question... is this meant only for use with dedicated > tap interfaces? Or will it be integrated with the mangement interface? > > Example... > > Today: > fxp0 - onboard NIC, 192.168.0.10, ssh, httpd, smtp, tcpdump, etc. > ixgbe0 - PCIe addon NIC, tap interface, netmap > > Tomorrow: > ixgbe0 - all the above functions in one NIC > > It would seem to me that an 'emulate an interface' shim/driver > could be written that would hook into netmap below and provide > all the normal interface semantics above. yes this is the long term plan (actually, kind of works now too if the netmap-attached client then passes the packets to the host stack). The tricky question is who select which (incoming) traffic needs to go to the host, and which one should be filtered out. I have some ideas but need to figure out what is the best way to go. > netmap interface <--> emulation driver <--> 'net0' interface > > So example... > > /etc/rc.conf:netmap_emulate1='ixgbe0 net0' > /etc/rc.conf:netmap_emulate2='em0 net1' > /etc/rc.conf:netmap_emulate3='fxp1 net2' > /etc/rc.conf:ifconfig_net0='inet 10.0.0.3/24' > ifconfig net0 192.168.0.10/24 -alias > ifconfig net0 ::1 > tcpdump, httpd, sshd, ... > ipfw, pf, netgraph, vlan, bridge, carp, ... > and all the other various capabilities of a physical NIC, etc... > > Also, though perhaps not needed for line rate capture, but for > making a standard interface to them... will various 10/100/1000 > NICS such as fxp, em, de, bfe, etc... end up being netmap capable? the em family is already supported. For the 100Mbit ports there is really no point, as CPUs are fast enough already. cheers luigi > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"