From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ia0-x234.google.com (mail-ia0-x234.google.com [IPv6:2607:f8b0:4001:c02::234]) (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 B8EB221F0BA for ; Sat, 4 May 2013 13:56:42 -0700 (PDT) Received: by mail-ia0-f180.google.com with SMTP id 21so1947780iay.25 for ; Sat, 04 May 2013 13:56:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=C2sQhvd7h/6pkCIKWWCThReq3rmEQQY6MtznTAv6wR0=; b=VAInR+Rz98bguoHEhl+Thvm3ea2egJ7nn0hvCFTeqYPm7IsIjo0uZNCP10Q9u5fTfO cDfx81fNSXsAkcnxj1VseNF4y5/pjbnx59V7pD6X3a49rOas5N3HDEmciwBuuY9MHf9m /+T6yG5PdVpN+iuKh3sR7pBKLufLwHLHwVj7Zp5uiKslFBIBTa9L1fxI6gppayrXj+G1 b54AQCgk3GTdSQciNB5iu0W1cA7jLWw8wKI+HcuHEuOQdKy7vRHa9a7K0VYgcdpSn8OK HriY87/Sqnoip+ZdEadjo4qe91K2ra7whpNe2j9Vn1UZhlAHPJxXbDo4OflMW02CflLr kcKw== MIME-Version: 1.0 X-Received: by 10.50.36.169 with SMTP id r9mr922434igj.96.1367701001883; Sat, 04 May 2013 13:56:41 -0700 (PDT) Received: by 10.64.7.51 with HTTP; Sat, 4 May 2013 13:56:41 -0700 (PDT) In-Reply-To: References: Date: Sat, 4 May 2013 13:56:41 -0700 Message-ID: From: Dave Taht To: Forums1000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: bloat Subject: Re: [Bloat] The bigger picture: what 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: Sat, 04 May 2013 20:56:43 -0000 On Thu, May 2, 2013 at 4:44 AM, Forums1000 wrote: > 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 anyon= e > 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). Or the algorithms need to be running on the bottleneck device. > 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 contribu= tes > 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. There are often many aggressive flows and it doesn't help to just shoot at one or drop a ton of packets from one, inside of an RTT. > > 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? Not true. Using a 5 tuple for udp works as well as it does for tcp. > Any good resources are more than welcome:-)! http://www.bufferbloat.net/projects/cerowrt/wiki/Bloat-videos > > Thanks, > Jeroen > > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat > --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html