From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <garmitage@swin.edu.au>
Received: from gpo1.cc.swin.edu.au (gpo1.cc.swin.edu.au [136.186.1.30])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by huchra.bufferbloat.net (Postfix) with ESMTPS id 0FC7E21F0FA
	for <bloat@lists.bufferbloat.net>; Sun, 10 Feb 2013 18:42:05 -0800 (PST)
Received: from [136.186.229.37] (garmitage.caia.swin.edu.au [136.186.229.37])
	by gpo1.cc.swin.edu.au (8.14.3/8.14.3) with ESMTP id r1B2g29O003858
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); 
	Mon, 11 Feb 2013 13:42:02 +1100
Message-ID: <51185A7A.2000708@swin.edu.au>
Date: Mon, 11 Feb 2013 13:42:02 +1100
From: grenville armitage <garmitage@swin.edu.au>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:16.0) Gecko/20121107 Thunderbird/16.0.2
MIME-Version: 1.0
To: bloat <bloat@lists.bufferbloat.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Bloat] Ethernet PAUSE frames, concatenated buffers
X-BeenThere: bloat@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: General list for discussing Bufferbloat <bloat.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bloat>
List-Post: <mailto:bloat@lists.bufferbloat.net>
List-Help: <mailto:bloat-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2013 02:42:06 -0000


So, Dave Taht suggested this might be of interest to some on
this list -- keep an eye out for consumer devices helpfully
using Ethernet PAUSE frames for layer 2 flow control.

We recently stumbled across this when exploring the behaviour of
a certain Netgear HomePlugAV (Ethernet over home powerline) device.
It was fun enough that the devices had a few thousand packets of
internal buffering. But when their buffer came close to full they'd
push-back with Ethernet PAUSE frames, forcing the next NIC upstream
(e.g. a host OS stack) to begin OS-specific buffering of outbound
Ethernet frames for a short while. This essentially concatenated the
HomePlugAV device's buffering with the sending host's NIC driver
buffering. Bufferbloat++

More details of our specific experiments can be found here,
http://caia.swin.edu.au/reports/130121A/CAIA-TR-130121A.pdf

cheers,
gja