From owner-freebsd-arch@FreeBSD.ORG Wed Mar 12 09:20:05 2008 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D6AD1065678 for ; Wed, 12 Mar 2008 09:20:05 +0000 (UTC) (envelope-from freebsd-arch@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 0D3758FC23 for ; Wed, 12 Mar 2008 09:20:05 +0000 (UTC) (envelope-from freebsd-arch@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1JZN7y-00046e-Io for freebsd-arch@freebsd.org; Wed, 12 Mar 2008 09:20:02 +0000 Received: from 195.208.174.178 ([195.208.174.178]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 Mar 2008 09:20:02 +0000 Received: from vadim_nuclight by 195.208.174.178 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 Mar 2008 09:20:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-arch@freebsd.org From: Vadim Goncharov Date: Wed, 12 Mar 2008 09:13:22 +0000 (UTC) Organization: Nuclear Lightning @ Tomsk, TPU AVTF Hostel Lines: 32 Message-ID: References: <86odacc04t.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 195.208.174.178 X-Comment-To: Dag-Erling =?koi8-r?Q?Sm=F8rgrav?= User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: Re: dev.* analogue for interfaces X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vadim_nuclight@mail.ru List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Mar 2008 09:20:05 -0000 Hi Dag-Erling Smørgrav! On Tue, 19 Feb 2008 18:43:46 +0100; Dag-Erling Smørgrav wrote about 'dev.* analogue for interfaces': > What I propose is to add a similar sysctl tree for interfaces. It would > look a little different. For instance, some interfaces (bridge, vlan) > have parents or children, but most don't. > Just as it is for devices, creation and destruction of the interface's > sysctl node and context would be hidden inside if_{attach,detach}() and > completely transparent to the driver, and there will be an API that > drivers can use if they want to add their own nodes. > Since interfaces don't all have parents, the API will include a function > to specify one for those that do. > This is *not* intended to replace ifconfig; it is intended for infor- > mation which isn't available through ifconfig and which it wouldn't be > natural to place there. For instance, every wlan interface already has > a sysctl tree under net.wlan. Will this allow to easier do things like adding new features in configuring per-interface network stack? To not bloat ifconfig, for example, to implement per-interface output DSCP->CoS map via sysctl subtree. Also, I'm not sure but think it will help virtualization, multiple routing tables, VRF and other things which can be bound to interface. So I agree with general idea, just actual info and position in tree should be discussed. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight]