From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (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 6D79821F454 for ; Mon, 2 Nov 2015 17:32:32 -0800 (PST) Received: by lfbn126 with SMTP id n126so1885253lfb.2 for ; Mon, 02 Nov 2015 17:32:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=g+OUM/Qn5AAil8Ck4XoEYqmSXfRA2rcsnP+BqG69GSU=; b=f3sZQ7IozUkiBRg47yZhwDTwkxLlZ+JZXu+PWkli2TvOc1msdFGz9kfLkIQ8/gchTD f9fIt7ujVix++IDh8YFNHRKRAYiOMBCApf443zbuIKG9yOcVWklBIMCA7JGeb6S5BzhT tF+ByCz6rnrrmdCSLApeycbI+P2O4xrrZEvWTkYsgX0dS9BConrfA+CRjgt/94kaCKGn nY+mHaY1WdiANbHJG+4Wm8q5XxzRImwZ1MN4nz1DK45TYuy2MzYy0MtGlRzo7T69w4iG jvXyiRgioEP/YdXccbP5Kt28ODb2tNCZ0CZm//3ZIqb40Fda+xX/hadyWexYaOYGANEC 6Ulw== X-Received: by 10.25.17.78 with SMTP id g75mr7761949lfi.12.1446514350423; Mon, 02 Nov 2015 17:32:30 -0800 (PST) Received: from bass.home.chromatix.fi (83-245-237-115-nat-p.elisa-mobile.fi. [83.245.237.115]) by smtp.gmail.com with ESMTPSA id m80sm4459536lfm.15.2015.11.02.17.32.29 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Nov 2015 17:32:29 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) From: Jonathan Morton In-Reply-To: <20151102165532.2e714f77@xeon-e3> Date: Tue, 3 Nov 2015 03:32:27 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <783C3A73-2535-431D-B794-CDDB542A956C@gmail.com> References: <20151029120038.03f09749@redhat.com> <20151102165532.2e714f77@xeon-e3> To: Stephen Hemminger X-Mailer: Apple Mail (2.3096.5) Cc: cake@lists.bufferbloat.net, Jesper Dangaard Brouer Subject: Re: [Cake] the meta problem of memory, locks, and multiple cpus X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2015 01:32:56 -0000 > On 3 Nov, 2015, at 02:55, Stephen Hemminger = wrote: >=20 > Why not measure the egress rate like PIE? Because there is often quite a lot of buffering in the device and/or = driver which can easily mask the true link rate, by absorbing bursts of = traffic at extremely high rates. This is a greater problem in ordinary = Ethernet NICs than in cable modems. It is likewise (and more obviously) = a problem when a fast Ethernet link exists between the router and a slow = last-mile modem. > Also many devices (like wifi) can't report real link rate. On the contrary, Minstrel knows what rate it has (momentarily) selected = for the wifi device to use (though it is then diluted by contention for = the medium). Exposing that to other layers of the network stack is the = challenge. - Jonathan Morton