From owner-p4-projects@FreeBSD.ORG Mon Sep 10 10:27:07 2007 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 8CF0B16A46C; Mon, 10 Sep 2007 10:27:07 +0000 (UTC) Delivered-To: perforce@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A06916A421 for ; Mon, 10 Sep 2007 10:27:07 +0000 (UTC) (envelope-from zec@icir.org) Received: from xaqua.tel.fer.hr (xaqua.tel.fer.hr [161.53.19.25]) by mx1.freebsd.org (Postfix) with ESMTP id D796213C465 for ; Mon, 10 Sep 2007 10:27:06 +0000 (UTC) (envelope-from zec@icir.org) Received: by xaqua.tel.fer.hr (Postfix, from userid 20006) id 997789B652; Mon, 10 Sep 2007 11:54:44 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on xaqua.tel.fer.hr X-Spam-Level: X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.7 Received: from [192.168.200.100] (zec2.tel.fer.hr [161.53.19.79]) by xaqua.tel.fer.hr (Postfix) with ESMTP id D9E119B644; Mon, 10 Sep 2007 11:54:43 +0200 (CEST) From: Marko Zec To: Julian Elischer Date: Mon, 10 Sep 2007 11:54:41 +0200 User-Agent: KMail/1.9.7 References: <200709092330.l89NUnVK097137@repoman.freebsd.org> <46E4A81E.1020703@elischer.org> In-Reply-To: <46E4A81E.1020703@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709101154.42412.zec@icir.org> Cc: Perforce Change Reviews Subject: Re: PERFORCE change 126243 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Sep 2007 10:27:07 -0000 On Monday 10 September 2007 04:12:46 Julian Elischer wrote: > Marko Zec wrote: > > In addition to ethernet/VLAN ifnets, allow for ng_iface > > ifnets to be reassigned from one vnet to another as well. > > I thought assignation was a property of all interfaces no matter what > the type? Some ifnet types have private structures that have trouble surviving if_detach()/if_attach() sequence called externaly on them. For example 802.11 ifnets typically hold bpf handles hidden somwhere inside their private state, and thus cannot be easily moved around vnets without modifying the drivers, and that is what I wish to avoid... For some other ifnets, say ppp(4) or sl(4), I'm not sure it would make much sense to reassign them from one vnet to another; others like gif/gre might need special handling to ensure "outer" and "inner" addresses live in proper vnets, until this is addressed properly I thought it might be better to disallow moving of such ifnets around vnets... Cheers, Marko