From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 30 05:57:45 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E723F16A4CE for ; Fri, 30 Jul 2004 05:57:45 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A9CB43D4C for ; Fri, 30 Jul 2004 05:57:45 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6U5sh0Q049142; Thu, 29 Jul 2004 23:54:43 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 29 Jul 2004 23:55:08 -0600 (MDT) Message-Id: <20040729.235508.112983217.imp@bsdimp.com> To: freebsd-hackers@freebsd.org, pawmal-posting@freebsd.lublin.pl From: "M. Warner Losh" In-Reply-To: <20040729201909.GA12370@shellma.zin.lublin.pl> References: <200407281145.27824.db@traceroute.dk> <200407281502.46395.max@love2party.net> <20040729201909.GA12370@shellma.zin.lublin.pl> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: max@love2party.net Subject: Re: Ready or not? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 05:57:46 -0000 In message: <20040729201909.GA12370@shellma.zin.lublin.pl> Pawel Malachowski writes: : On Wed, Jul 28, 2004 at 03:02:38PM +0200, Max Laier wrote: : : Hello, : : > as PF+ALTQ gateway in production environment. For ALTQ there is the problem : > of "will your driver be supported?". : : Could You please explain a bit, why ALTQ model is placed so close : to network adapter driver (that they have to be modified) instead : of placing it in upper layers (and leaving NIC drivers untouched)? The short answer is because there is buffering (queueing) in the NIC layer, and that limits the ability of of ALTQ to do its job. In order to do QoS type things, this queueing makes it harder without the help of the NIC driver. It is more complicated than this (I don't understand all the details), but that is the jist of a larger presentation of ALTQ that I had the pleasure of viewing at AsiaBSDcon. Warner