From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-bk0-x229.google.com (mail-bk0-x229.google.com [IPv6:2a00:1450:4008:c01::229]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 4912421F1A1 for ; Thu, 11 Jul 2013 12:41:23 -0700 (PDT) Received: by mail-bk0-f41.google.com with SMTP id jc3so3560903bkc.28 for ; Thu, 11 Jul 2013 12:41:21 -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=6bViCqfJHIOA2juojOuVYax4CfGlWl5BUbxWrSx8HMw=; b=YVttfVuA0uEshoQIBChtBH+uhpGxF/AtISV3JAZCexYf9IRa9hX15uYxAHItNBQKBB NalMBRLF7EVUuIvCXAnj+lsK4V0Q+YljjFzSx4X5byifQLlk1z04oKZnZMzzsP38Fmih 6QdmLphGqwoyJ7gdD5gTA2sS6Is4brmRyiQxUHm984fsoPsvCdfxj8LUhoIyqaj+YGyt Gzbngrmmpvm9dL8X7iDBW2AAILLfqs3/+Lj2RwEW8jrMeGTmHDtFdnbske4SGZeyRfm4 /AIAhWdc7wfpstRQqfSWn68P5MUmi2FNCWSjq3iiXla9Xl530Vl4JTHa5MOxCtHME2le 4v2Q== MIME-Version: 1.0 X-Received: by 10.205.9.8 with SMTP id ou8mr6015346bkb.76.1373571680913; Thu, 11 Jul 2013 12:41:20 -0700 (PDT) Received: by 10.205.75.67 with HTTP; Thu, 11 Jul 2013 12:41:20 -0700 (PDT) Received: by 10.205.75.67 with HTTP; Thu, 11 Jul 2013 12:41:20 -0700 (PDT) In-Reply-To: References: <1373564673.4600.55.camel@edumazet-glaptop> Date: Thu, 11 Jul 2013 22:41:20 +0300 Message-ID: From: Jonathan Morton To: Dave Taht Content-Type: multipart/alternative; boundary=20cf301cc6041d7d0304e1419422 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: Thu, 11 Jul 2013 19:41:23 -0000 --20cf301cc6041d7d0304e1419422 Content-Type: text/plain; charset=ISO-8859-1 > 4) ECN processing is enabled by default (but off by default in sysctl) I don't see any harm in handling ECN correctly in the qdisc at all times. It is routers that screw it up that require ECN negotiation to be disabled at the endpoints by default - I assume that's the sysctl you're referring to. The more ECN traffic there is in the wild, the more visible the problems will be with the broken routers, and the greater the likelihood that they might actually get fixed. And the greater benefit perceived to be attached to ECN by end users and net admins, the more likely they are to actually turn it on. - Jonathan Morton --20cf301cc6041d7d0304e1419422 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

> 4) ECN processing is enabled by default (but off by def= ault in sysctl)

I don't see any harm in handling ECN correctly in the qd= isc at all times. It is routers that screw it up that require ECN negotiati= on to be disabled at the endpoints by default - I assume that's the sys= ctl you're referring to.

The more ECN traffic there is in the wild, the more visible = the problems will be with the broken routers, and the greater the likelihoo= d that they might actually get fixed. And the greater benefit perceived to = be attached to ECN by end users and net admins, the more likely they are to= actually turn it on.

- Jonathan Morton

--20cf301cc6041d7d0304e1419422--