From owner-freebsd-net@FreeBSD.ORG Wed Mar 19 11:23:21 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 D6A59C09 for ; Wed, 19 Mar 2014 11:23:21 +0000 (UTC) Received: from smtp1.bushwire.net (f5.bushwire.net [199.48.133.46]) by mx1.freebsd.org (Postfix) with SMTP id 8961C8F7 for ; Wed, 19 Mar 2014 11:23:20 +0000 (UTC) Received: (qmail 94230 invoked by uid 1001); 19 Mar 2014 11:16:38 -0000 Delivered-To: qmda-intercept-freebsd-net@freebsd.org DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=s384; d=romeo.emu.st; b=NbvrnPGHnOh2i/J3Q+KKpgufsbMcgIjdcpF3oOUr4+IwsABjNqmDxJrYqYKaQ4K8; Comments: DomainKeys? See http://en.wikipedia.org/wiki/DomainKeys DomainKey-Trace-MD: h=10; b=31; l=C18R71D32M65F38T27S42M17C39C27; Comments: QMDA 0.3 Received: (qmail 94223 invoked by uid 1001); 19 Mar 2014 11:16:38 -0000 Date: 19 Mar 2014 11:16:38 +0000 Message-ID: <20140319111638.94222.qmail@f5-external.bushwire.net> From: "Mark Delany" To: freebsd-net@freebsd.org Subject: Minor nits with netmap(4) manpage MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 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, 19 Mar 2014 11:23:21 -0000 (Luigi's page suggests posting here.) Very recent freebsd10 (r263256) 1) the manpage says "SEE TRANSPARENT MODE" but no such section exists. 2) the manpage refers to NR_RING_NIC_SW when I think it means NR_REG_NIC_SW. 3) No mention is made of access control. I think earlier documentation suggested that you had to run as root, but now it appears to work for any user that has rw access to /dev/netmap. Obvious I guess but just mentioning that access is controlled by the file system, not your uid. 4) epoll/kqueue has conflicting information. An early para says "... and standard OS mechanisms such as select(2), poll(2), epoll(2), kqueue(2)." But a later para says "epoll(2) and kqueue(2) are not supported on netmap file descriptors.". On the matter of transparent mode, it seems that all an application has to do to have a packet proceed up into the host stack is set NS_FORWARD in the ring flags. That's a super-nice feature as is netmap in general. Mark.