From owner-freebsd-arch@FreeBSD.ORG  Sun Jul  9 19:12:19 2006
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
X-Original-To: freebsd-arch@freebsd.org
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7510E16A4DA
	for <freebsd-arch@freebsd.org>; Sun,  9 Jul 2006 19:12:19 +0000 (UTC)
	(envelope-from sam@errno.com)
Received: from ebb.errno.com (ebb.errno.com [69.12.149.25])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2050743D45
	for <freebsd-arch@freebsd.org>; Sun,  9 Jul 2006 19:12:18 +0000 (GMT)
	(envelope-from sam@errno.com)
Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248])
	(authenticated bits=0)
	by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k69JCHYZ082260
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <freebsd-arch@freebsd.org>; Sun, 9 Jul 2006 12:12:18 -0700 (PDT)
	(envelope-from sam@errno.com)
Message-ID: <44B15511.206@errno.com>
Date: Sun, 09 Jul 2006 12:12:17 -0700
From: Sam Leffler <sam@errno.com>
User-Agent: Thunderbird 1.5.0.2 (X11/20060508)
MIME-Version: 1.0
To: freebsd-arch@freebsd.org
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: vlans and cloning
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jul 2006 19:12:19 -0000

I committed the revised netif cloning api so you can now specify
parameters when cloning.  I also modified the vlan code to use this
mechanism so doing something like:

ifconfig vlan create vlan 1 vlandev em0

causes a single request to clone a vlan together with the tag+parent
device parameters (i.e. and no subsequent SIOCSETVLAN request).

Given the above do we still need to support setting vlan tag+device
separately or can we just require everything be specified when doing the
clone operation?  This would change the user api but otherwise I can see
no reason for continuing to support the old mechanism where you do:

ifconfig vlan create
ifconfig vlan0 vlan 1 vlandev em0

Anyone _against_ nuking the above?

	Sam