From owner-freebsd-net@FreeBSD.ORG Fri Jun 14 10:05:26 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DF321B4F; Fri, 14 Jun 2013 10:05:26 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id A5EE813CA; Fri, 14 Jun 2013 10:05:26 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id CF89F7300B; Fri, 14 Jun 2013 12:08:28 +0200 (CEST) Date: Fri, 14 Jun 2013 12:08:28 +0200 From: Luigi Rizzo To: Gleb Smirnoff Subject: Re: [PATH] ALTQ(9) codel algorithm implementation Message-ID: <20130614100828.GA48119@onelab2.iet.unipi.it> References: <20130614095125.GQ12443@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130614095125.GQ12443@FreeBSD.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Ermal Lu?i , freebsd-net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jun 2013 10:05:26 -0000 On Fri, Jun 14, 2013 at 01:51:25PM +0400, Gleb Smirnoff wrote: > Ermal, ... > I'm afraid we can't grow mbuf packet header with 8 bytes just to satisfy > the ALTQ codel algo, which would definitely have a limited usage among > FreeBSD users. Thus, "enqueue_time" should go into mbuf_tags(9) not into > mbuf packet header. not to take positions one way or the other, but getting and releasing a tag on every packet is going to kill performance. If i remember well, 2-3 years ago at bsdcan there was discussion (and mention of some pending work, jeffr maybe ?) on providing some leading space in the mbuf so one could put there tags (e.g. ipfw and dummynet ones) without having to allocate them. Not sure where is this. The other thing with codel is that it needs a fairly coarse timer resolution (100us..1ms) to work so one might be happy with shorter timestamps (e.g. 4 bytes) if space allows them. cheers luigi