From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by huchra.bufferbloat.net (Postfix) with ESMTP id B4DF021F1AB for ; Mon, 15 Jul 2013 07:24:50 -0700 (PDT) Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r6FEOi3H022734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 15 Jul 2013 10:24:44 -0400 Received: from localhost (ovpn-116-55.ams2.redhat.com [10.36.116.55]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r6FEOgxf003290; Mon, 15 Jul 2013 10:24:42 -0400 Date: Mon, 15 Jul 2013 16:24:39 +0200 From: Jesper Dangaard Brouer To: Eric Dumazet , Stephen Hemminger , Dave Taht Message-ID: <20130715162439.0bc86ff2@redhat.com> In-Reply-To: <1373896674.10804.73.camel@edumazet-glaptop> References: <1373564673.4600.55.camel@edumazet-glaptop> <1373568848.4600.66.camel@edumazet-glaptop> <20130712113413.4b601800@redhat.com> <1373642001.10804.18.camel@edumazet-glaptop> <1373648057.10804.29.camel@edumazet-glaptop> <20130715154009.4c0d4531@redhat.com> <1373896674.10804.73.camel@edumazet-glaptop> Organization: Red Hat Inc. Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24 Cc: codel@lists.bufferbloat.net Subject: Re: [Codel] hardware multiqueue in fq_codel? 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, 15 Jul 2013 14:24:51 -0000 On Mon, 15 Jul 2013 06:57:54 -0700 Eric Dumazet wrote: > On Mon, 2013-07-15 at 15:40 +0200, Jesper Dangaard Brouer wrote: > > > Then they should also be smart enough to change their default > > fq_codel qdisc, to be a prio band based qdisc... shouldn't they ;-) > > > > Some companies do this classification at the edge of their network, so > that they do not have to worry for each machine of their fleet. > > Forcing them to learn how to 'fix' things once a new linux version is > installed would be quite lame. I wont be the guy responsible for this. Agreed. (And at big companies the network-router-guys and sysadm-guys are different people/groups, thus harder to coordinate this change. I was mostly trolling ;-)) > Listen, there is no point trying to tell me how fq_codel is better > than pfifo_fast. Is an apple better than an orange ? > > Instead, we only have to create a clear path. > > 1) Allow the default qdisc to be specified/chosen in Kconfig, a bit > like tcp congestion module (cubic is the default) > > 2) Allow the default qdisc to be selected by a /proc/sys entry, like > TCP congestion module. > > 3) Define the PRIO + codel/band0 + fq_codel/band1 + codel/band2 as a > new standalone qdisc > > 4) Eventually switch the default Kconfig from pfifo_fast to this > beast. Agreed, sounds like a good plan to me, Dave? -- Best regards, Jesper Dangaard Brouer MSc.CS, Sr. Network Kernel Developer at Red Hat Author of http://www.iptv-analyzer.org LinkedIn: http://www.linkedin.com/in/brouer