From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from g4t3428.houston.hp.com (g4t3428.houston.hp.com [15.201.208.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 5DB3B3B2BD; Thu, 17 Mar 2016 13:24:49 -0400 (EDT) Received: from g4t3433.houston.hp.com (g4t3433.houston.hp.com [16.210.25.219]) by g4t3428.houston.hp.com (Postfix) with ESMTP id A2E4F5B; Thu, 17 Mar 2016 17:24:48 +0000 (UTC) Received: from [16.103.148.51] (tardy.usa.hp.com [16.103.148.51]) by g4t3433.houston.hp.com (Postfix) with ESMTP id AB54F4C; Thu, 17 Mar 2016 17:24:47 +0000 (UTC) To: Dave Taht , Michal Kazior References: <1458123478-1795-1-git-send-email-michal.kazior@tieto.com> <20160316185531.GA1771@localhost> Cc: Network Development , linux-wireless , "ath10k@lists.infradead.org" , Jasmine Strong , "codel@lists.bufferbloat.net" , make-wifi-fast@lists.bufferbloat.net From: Rick Jones Message-ID: <56EAE85F.3010407@hpe.com> Date: Thu, 17 Mar 2016 10:24:47 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 25 Mar 2016 11:52:32 -0400 Subject: Re: [Make-wifi-fast] [Codel] [RFCv2 0/3] mac80211: implement fq codel X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Mar 2016 17:24:49 -0000 On 03/17/2016 10:00 AM, Dave Taht wrote: > netperf's udp_rr is not how much traffic conventionally behaves. It > doesn't do tcp slow start or congestion control in particular... Nor would one expect it to need to, unless one were using "burst mode" to have more than one transaction inflight at one time. And unless one uses the test-specific -e option to provide a very crude retransmission mechanism based on a socket read timeout, neither does UDP_RR recover from lost datagrams. happy benchmarking, rick jones http://www.netperf.org/