From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 91F243CB35 for ; Wed, 29 Nov 2017 10:44:54 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1511970291; bh=AVV7ackYlXoaSqidUHxdpXbM25KuvGQQNi/DeNJ1rIg=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=sc6pEi9yQEwh2iGpPREcXM2jw6L/vIQqR5EYBbFDRXuyrsRUnuyBlY1+fblFNw9wO YEE6Jh7vFFSOXbpdPJmJfDQUtg93mBdWXX4jVJ9xmQbgY8t8MPuxX/AgWkBrWvx7yt gx/55CMiF0dd0GGS+NwFe598whAr6i0apu20Ueb5LAcctZgHuRhC303CzmfUcW8j+D THX+yxeFeUfDc6XO+Jc0Hdg6/bzNTG39LOxBDKyxiWRunYmrRXDX0MRs29F/IuQ3gI fezeMeAbdE7bIMz73ViCrmQQiqS4hajfLHpOrkioqFTWU1I38nLkyG9ulWSeTyE1r6 LMgZoh24EQsyQ== To: Pete Heist , Georgios Amanakis Cc: Cake List In-Reply-To: <20760855-77A6-456D-BFDB-2A5D17C4528A@gmail.com> References: <745FEC66-95A7-40E1-A8FA-57714D3AB6AC@gmail.com> <87zi76xlw5.fsf@nemesis.taht.net> <6F2894AD-87EA-4EFC-918E-625E49EDA977@gmail.com> <87o9nmxcbg.fsf@nemesis.taht.net> <87bmjmxbgw.fsf@nemesis.taht.net> <3FAFACA8-C918-4325-BF80-B7EBB6B9B4A7@gmail.com> <87k1y96swh.fsf@toke.dk> <20760855-77A6-456D-BFDB-2A5D17C4528A@gmail.com> Date: Wed, 29 Nov 2017 16:44:50 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <878tep6qdp.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Cake] cake flenter results round 2 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: Wed, 29 Nov 2017 15:44:54 -0000 > (That was also informative for me about how netperf decides when to > emit a data point=E2=80=A6) In that case I can add that the stated reason for this way of doing things is performance (i.e., emitting data points should not interfere with transfer performance). This is mostly an issue on systems where getting time is expensive; which is not the case on modern Linux systems. But I'm not entirely sure that the optimisation only has historical reasons; it may be that some systems supported by Netperf still has this issue... -Toke