From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 90B5C21F1EE for ; Sat, 28 Sep 2013 22:49:26 -0700 (PDT) Received: by mail-we0-f175.google.com with SMTP id q59so4287841wes.34 for ; Sat, 28 Sep 2013 22:49:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nFEU65Ryo/mq0Ihd6LkO7ARLx3cdCs9VvgKD0bwfCOg=; b=uOj5WZ9QL0r2seh0MJCxZtgA5p4qv7XmhGVUwB1j/fs7eMJ+9OQA4jW9tH4JqdWWhm ShRhwTETjFOwhdP+P/4/K1r4IupmqLTl+rjwAkB7tNevNIW9M4uQppmi4QDCPYJiVjnF OZpebJHenEwjSeBr54EFrkG+sh5r/Tj905kL/Ou0zT3mpg7SJlKQ34zecQ8I+zfz91e2 MMWF0sSViMCmoKVop4kVpYpvWXHoZGceWMgWJ/5q9jtA5yQIyL1e9kWRxtZiMz0vGs6U zZuJ2BZ4npalnx0hp2mHsuqbONzxT2B/L+Y2fIH5wDvCKWOMblRnbgk7wIdI9Mi9oO3x pyKw== MIME-Version: 1.0 X-Received: by 10.180.198.227 with SMTP id jf3mr8766942wic.19.1380433764050; Sat, 28 Sep 2013 22:49:24 -0700 (PDT) Received: by 10.217.67.202 with HTTP; Sat, 28 Sep 2013 22:49:23 -0700 (PDT) Received: by 10.217.67.202 with HTTP; Sat, 28 Sep 2013 22:49:23 -0700 (PDT) In-Reply-To: <1380128313.3165.157.camel@edumazet-glaptop> References: <2719938E-E24A-4A06-898F-CE90CBED005C@inria.fr> <1380122152.3165.156.camel@edumazet-glaptop> <5243036F.90302@orange.com> <1380128313.3165.157.camel@edumazet-glaptop> Date: Sun, 29 Sep 2013 06:49:23 +0100 Message-ID: From: Dave Taht To: Eric Dumazet Content-Type: multipart/alternative; boundary=047d7b622588246cb604e77f48f2 Cc: aqm@ietf.org, bloat Subject: Re: [Bloat] [aqm] TSO sizing fixes and the new paced "fq" scheduler in Linux 3.12 X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Sep 2013 05:49:27 -0000 --047d7b622588246cb604e77f48f2 Content-Type: text/plain; charset=ISO-8859-1 On Sep 25, 2013 9:58 AM, "Eric Dumazet" wrote: > > On Wed, 2013-09-25 at 17:38 +0200, Luca MUSCARIELLO wrote: > > > Then, I feel like FQ is a bad name to call this "newFQ". > > It's an implementation of a fair TCP pacer. Which is very useful, but FQ > > is kind of misleading, IMHO. > > No problem, feel free to send a patch. I am very bad at choosing names. Fair TCP pacer = ftp # taken Paced fair queue = pfq # lit collision Enhanced paced queue = epq # pronounced epic! > > --047d7b622588246cb604e77f48f2 Content-Type: text/html; charset=ISO-8859-1


On Sep 25, 2013 9:58 AM, "Eric Dumazet" <eric.dumazet@gmail.com> wrote:
>
> On Wed, 2013-09-25 at 17:38 +0200, Luca MUSCARIELLO wrote:
>
> > Then, I feel like FQ is a bad name to call this "newFQ".
> > It's an implementation of a fair TCP pacer. Which is very useful, but FQ
> > is kind of misleading, IMHO.
>
> No problem, feel free to send a patch. I am very bad at choosing names.

Fair TCP pacer = ftp # taken
Paced fair queue = pfq # lit collision
Enhanced paced queue = epq # pronounced epic!
>
>

--047d7b622588246cb604e77f48f2--