From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ee0-f48.google.com (mail-ee0-f48.google.com [74.125.83.48]) (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 C515A21F18F for ; Thu, 2 May 2013 04:43:32 -0700 (PDT) Received: by mail-ee0-f48.google.com with SMTP id d4so222730eek.7 for ; Thu, 02 May 2013 04:43:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=dBDFru8+KvaBtzpAPoa9L+7GIwJgtR3Q5VupF1HpMqc=; b=dNbqi+6VC8in21ggN1LOW/n5F2RWRWPat2CJKirX3YypMKUQ6xiNrUNLOwv0yyxBLe ueJXOvYP+YOH1rHijjyHQNE5M4VlgmDCge73NLCD6/rdlJ/9+4UVgzC2fP7KLV9UtuGa cz804ULhcQPRj7SWnsxExQX9xYv6f+uo7SENFYAbf1UFZj2IfYbOKFDTNbFOakEf2T8R 5XK3iiay3tjhqM+grRsy6uwjTA5w3Z1LDq3XCDJVpx3H7bNg4LAWxVnIlyGCWCCH1y5D TndsWKbk6bqMOG01SMOgW0OetwZW+WDJ4dVsVY2yfCk7YoK6SfQ6qitmXX1LpxhX6mWq pg9g== X-Received: by 10.14.109.131 with SMTP id s3mr18711482eeg.26.1367495010552; Thu, 02 May 2013 04:43:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.14.145.79 with HTTP; Thu, 2 May 2013 04:43:00 -0700 (PDT) From: Jeroen Balduyck Date: Thu, 2 May 2013 13:43:00 +0200 Message-ID: To: bloat Content-Type: multipart/alternative; boundary=001a11c29f7e56384304dbbabeb1 Subject: [Bloat] The bigger picture: whats components are used together to fight bloat 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: Thu, 02 May 2013 11:43:33 -0000 --001a11c29f7e56384304dbbabeb1 Content-Type: text/plain; charset=ISO-8859-1 I hope I can get a bit more information on what comprises the total solution. But knitting it together proves a bit hard (for me at least). Without this, it is hard to follow the discussions on the list. Has anyone made a summary of how all of this works together? So: 1. In order to move the bottleneck to a device under our administrative control, we need to shape traffic (we need to become the bottleneck). 2. Next, we have the AQM-algorithms that manage the (or a) queue. 3. And then there are still issues with multiple flows and with UDP? >From what I understand, we need to shape traffic, and then drop packets taking into account that the most aggressive flow (the flow that contributes the most to filling a buffer), is the flow that will get the most packets dropped. This to prevent the aggressive flow from impacting flows that behave better. Now for UDP, is the problem here that we cannot identify flows, and hence, only have one queue for UDP whereas for TCP we can have multiple? Any good resources are more than welcome:-)! Thanks, Jeroen --001a11c29f7e56384304dbbabeb1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I hope I can get a bit more information on what compr= ises the total solution. But knitting it together proves a bit hard (for me= at least). Without this, it is hard to follow the discussions on the list.= Has anyone made a summary of how all of this works together?

So:

1. In order to move the bottleneck to a device un= der our administrative control, we need to shape traffic (we need to become= the bottleneck).
2. Next, we have the AQM-algorithms that manage the (= or a) queue.
3. And then there are still issues with multiple flows and with = UDP?

From what I understand, we need to shape traffic, an= d then drop packets taking into account that the most aggressive flow (the = flow that contributes the most to filling a buffer), is the flow that will = get the most packets dropped. This to prevent the aggressive flow from impa= cting flows that behave better.

Now for UDP, is the problem here that we cannot identify flo= ws, and hence, only have one queue for UDP whereas for TCP we can have mult= iple?

Any good resources are more than welcome:-)!

Thanks,
Jeroen
--001a11c29f7e56384304dbbabeb1--