From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (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 0AE4321F1FA for ; Thu, 20 Mar 2014 12:34:16 -0700 (PDT) Received: by mail-ig0-f175.google.com with SMTP id ur14so15849614igb.2 for ; Thu, 20 Mar 2014 12:34:15 -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=6x1B35vpk0qQuRCbzRAslgbk+AITpxtrR54shkRi0fY=; b=tReEDCsb8FxRTB0OKFBd8HbsNPMfHYG+wtNGw5SDPmv2mnOiug7iBBz9ysEbp8TA62 ahP3yxWCKRkhgAj9d7J+z4g8kg9EqVYZ0P763EXtfzlJveWZsKpB2B8KiqcEdF+50Ekw SC/A1rPuJVnHZeeeOc2lxoNB/i6L+HUVJ8J7ckz4QyNTsPYxbs9YOANb0WuVF1G8JWDC gIMqudMFlc6MOJMQvMggg8v9ef17d2psFT0vwXTzoj+Joox0uAbl5N2tafYJZZnZzjkR N3bGnbnPsCiQd/OYbDdDtAH/C+yGMzkmPYG+nk5zhNNecnafW6ibhtnLAhu4Ot4WjnTY vvew== MIME-Version: 1.0 X-Received: by 10.42.82.148 with SMTP id d20mr18211741icl.50.1395344055366; Thu, 20 Mar 2014 12:34:15 -0700 (PDT) Received: by 10.64.238.70 with HTTP; Thu, 20 Mar 2014 12:34:15 -0700 (PDT) In-Reply-To: References: <20140318145221.GA31327@sesse.net> <07BD4518-2A7E-4F43-8978-791E3B2BDA2A@cisco.com> <87eh1wc05c.fsf@toke.dk> <87a9ckbz1q.fsf@toke.dk> Date: Thu, 20 Mar 2014 12:34:15 -0700 Message-ID: From: Aaron Wood To: Dave Taht Content-Type: multipart/alternative; boundary=90e6ba613a1ec27bc604f50eda67 Cc: bloat Subject: Re: [Bloat] AQM creeping into L2 equipment 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, 20 Mar 2014 19:34:16 -0000 --90e6ba613a1ec27bc604f50eda67 Content-Type: text/plain; charset=ISO-8859-1 > > however what we are probably seeing with the measurement flows is > slow start causing a whole bunch of packets to be lost in a bunch. > That would line up with the timing, and the periodic drops that I see in the flows when using Toke's newer wrapper (and netperf head), which attempt to work around the failing UDP timing flows. -Aaron --90e6ba613a1ec27bc604f50eda67 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
however what we are probably seeing with the mea= surement flows is
slow start causing a whole bunch of packets to be lost in a bunch.

That would line up with the timing, and the per= iodic drops that I see in the flows when using Toke's newer wrapper (an= d netperf head), which attempt to work around the failing UDP timing flows.= =A0

-Aaron
--90e6ba613a1ec27bc604f50eda67--