From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from g1t0029.austin.hp.com (g1t0029.austin.hp.com [15.216.28.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smtp.hp.com", Issuer "VeriSign Class 3 Secure Server CA - G3" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id ED766201A91 for ; Mon, 7 May 2012 10:27:23 -0700 (PDT) Received: from g1t0039.austin.hp.com (g1t0039.austin.hp.com [16.236.32.45]) by g1t0029.austin.hp.com (Postfix) with ESMTP id 89E8A380E3; Mon, 7 May 2012 17:27:22 +0000 (UTC) Received: from [16.89.64.213] (tardy.cup.hp.com [16.89.64.213]) by g1t0039.austin.hp.com (Postfix) with ESMTP id DE8A2340EF; Mon, 7 May 2012 17:28:19 +0000 (UTC) Message-ID: <4FA805F9.20004@hp.com> Date: Mon, 07 May 2012 10:27:21 -0700 From: Rick Jones User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Eric Dumazet References: <1336246349-20228-1-git-send-email-dave.taht@bufferbloat.net> <4FA7FBC7.2040501@hp.com> <1336410626.3752.2329.camel@edumazet-glaptop> In-Reply-To: <1336410626.3752.2329.camel@edumazet-glaptop> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: Eric Dumazet , codel@lists.bufferbloat.net, Dave Taht Subject: Re: [Codel] [PATCH 1/2] codel: Controlled Delay AQM X-BeenThere: codel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: CoDel AQM discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2012 17:27:24 -0000 On 05/07/2012 10:10 AM, Eric Dumazet wrote: > On Mon, 2012-05-07 at 09:43 -0700, Rick Jones wrote: >> On 05/05/2012 12:32 PM, Dave Taht wrote: >>> From: Dave Täht >>> >>> tc qdisc ... codel [ limit PACKETS ] [ target TIME] >>> [ interval TIME ] [ minbytes BYTES ] >> >> Usability suggestions - "target_latency" or "target_lat" and >> "action_interval" or "decision_interval" perhaps? > > We took the terms used in the codel paper. > > By the way, target is not target_latency, its more a target threshold > (packets under it are not dropped), but packets above might be dropped. I don't wish to rathole, and someone may want to declare Bikeshed! but the target audience of the paper is a bit different from the Linux system administrator base yes? If a parameter name enhancement makes something more clear to an administrator is it really a bad thing to have a name that is not a strict duplicate of the paper's? rick