From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from g2t2355.austin.hpe.com (g2t2355.austin.hpe.com [15.233.44.28]) (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 6439F3B260; Fri, 20 May 2016 12:20:29 -0400 (EDT) Received: from g2t2360.austin.hpecorp.net (g2t2360.austin.hpecorp.net [16.196.225.135]) by g2t2355.austin.hpe.com (Postfix) with ESMTP id 7753851; Fri, 20 May 2016 16:20:28 +0000 (UTC) Received: from [16.103.148.51] (tardy.usa.hp.com [16.103.148.51]) by g2t2360.austin.hpecorp.net (Postfix) with ESMTP id E86203A; Fri, 20 May 2016 16:20:27 +0000 (UTC) To: Jonathan Morton , David Lang References: <22371476-B45C-4E81-93C0-D39A67639EA0@gmx.de> <991C8B50-192E-431A-819F-F1C5954FF64F@gmx.de> <4C5D0005-2CAA-4C90-BF0D-7177874872AC@gmail.com> Cc: cake@lists.bufferbloat.net, codel@lists.bufferbloat.net From: Rick Jones Message-ID: <573F394B.5060009@hpe.com> Date: Fri, 20 May 2016 09:20:27 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <4C5D0005-2CAA-4C90-BF0D-7177874872AC@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Fri, 20 May 2016 12:30:45 -0400 Subject: Re: [Cake] [Codel] Proposing COBALT X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2016 16:20:29 -0000 On 05/20/2016 08:12 AM, Jonathan Morton wrote: > >> On 20 May, 2016, at 17:04, David Lang wrote: >> >> Is it possible to get speed testing software to detect that it's receiving fragments and warn about that? > > Do iperf3’s maintainers accept patches? Netperf's maintainer has been known to accept patches so long as they aren't too hairy. That said, it isn't clear how something operating above the socket interface is going to know that the traffic it was receiving was in the form of reassembled IP datagram fragments. happy benchmarking, rick jones I suppose if said software were to dive below the socket interface it could find-out, though that will tend to lack portability.