From owner-freebsd-net@FreeBSD.ORG Sun Feb 13 23:06:44 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7757516A4CE for ; Sun, 13 Feb 2005 23:06:44 +0000 (GMT) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47ADD43D53 for ; Sun, 13 Feb 2005 23:06:44 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with SMTP id 2705E46B16; Sun, 13 Feb 2005 18:06:43 -0500 (EST) Date: Sun, 13 Feb 2005 23:05:27 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: David Gilbert In-Reply-To: <16911.51264.86063.604597@canoe.dclg.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: altq for vlans? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2005 23:06:44 -0000 On Sun, 13 Feb 2005, David Gilbert wrote: > Has anyone considered patching the vlan driver to support altq? I > gather that since tun works, so should vlan. My understanding is that ALTQ processing occurs in the context of persisting outgoing packet queues -- the queueing going into the vlan driver is minimal, as the vlan driver immediately hands packets off to the underlying driver output queue. As such, my guess is that (a) there would be little or no effect to adding ALTQ processing the vlan interfaces since packets only ever live fleetingly in vlan queues, and (b) ALTQ processing already happens on the underlying interface, so you probably don't need it at the vlan layer, although you might look at vlan tags in deciding how to drop/etc the vlan-sourced messages in the underlying interface queue. Robert N M Watson