From owner-freebsd-current@FreeBSD.ORG Thu Apr 12 21:28:50 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0FA1716A404 for ; Thu, 12 Apr 2007 21:28:50 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by mx1.freebsd.org (Postfix) with ESMTP id EBB8D13C46C for ; Thu, 12 Apr 2007 21:28:49 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay8.apple.com (relay8.apple.com [17.128.113.38]) by mail-out4.apple.com (8.13.8/8.13.8) with ESMTP id l3CLSnSO017086; Thu, 12 Apr 2007 14:28:49 -0700 (PDT) Received: from relay8.apple.com (unknown [127.0.0.1]) by relay8.apple.com (Symantec Mail Security) with ESMTP id BC23640080; Thu, 12 Apr 2007 14:28:49 -0700 (PDT) X-AuditID: 11807126-9ed4dbb0000007ff-a5-461ea491e969 Received: from [17.214.13.96] (cswiger1.apple.com [17.214.13.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay8.apple.com (Apple SCV relay) with ESMTP id A752E4005B; Thu, 12 Apr 2007 14:28:49 -0700 (PDT) In-Reply-To: <20070412210957.GA31864@heff.fud.org.nz> References: <20070411191450.GE815@turion.vk2pj.dyndns.org> <20070412210957.GA31864@heff.fud.org.nz> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Thu, 12 Apr 2007 14:28:48 -0700 To: Andrew Thompson X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== Cc: freebsd-current@freebsd.org Subject: Re: CFT: new trunk(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2007 21:28:50 -0000 On Apr 12, 2007, at 2:09 PM, Andrew Thompson wrote: > On Thu, Apr 12, 2007 at 07:39:00AM +0200, Ian FREISLICH wrote: >> Peter Jeremy wrote: >>> Trunking is a way of combining multiple physical interfaces to >>> increase >>> the bandwidth. Trunking multiple VLANs on a single interface >>> doesn't >>> make sense to me. >> >> 802.1q is VLAN tagging and trunking. This interface is LACP - link >> aggregation. I really think that it makes no sense to be able to >> aggregate some ethernet interfaces and not others. I suppose some >> pedant will tell me vlan interfaces are not ethernet. > > I think the unfortunate name of trunk(4) that we inherited from > OpenBSD > is causing quite some confusion. trunk(4) actually has nothing to do > with vlan trunking which I think you are after. Yup. The term "trunk" is overloaded and can used both in the sense of "trunk port", meaning a port on a switch which exposes the VLAN tags and is usually used to connect several VLANs between two switches (in contrast to an end-station port which only gets ethernet frames for the VLAN ID(s) assigned to that port), yet is also used by vendors like 3com in phrases like "trunk groups" or "port trunking", which means the same thing that Cisco means with FEC (ie, IEEE 802.3ad or the LACP term mentioned above). > I can see this topic coming up again so it could save some time to > rename the driver now. It would mean that we lose the naming link > to the > same driver in OpenBSD but you cant win em all. > > Some names that have been suggested are: > > linkag(4) > agr(4) > bond(4) <- same as linux > > Any suggestions! lacp(4)...? bond(4) also seems OK, and perhaps is a more intuitive name; agr(4) strikes me as being too likely to be confused with some odd flavor of NIC or agpgart(4). -- -Chuck