From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 4A49A3B2A3; Mon, 30 Jan 2017 17:48:46 -0500 (EST) Received: by mail-wm0-x230.google.com with SMTP id v77so69053682wmv.0; Mon, 30 Jan 2017 14:48:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=C0sVaTm+B21rKUzxdJ7/QIaWSZq9jvviQexIVMnLhn4=; b=M5ClmVJ/WKE+8lutw+VYObZwz+N7A6G9I3MKD+UlZ39CtivL/rjo1lVxxvnYFY8gpc f3/EN5o7lWFM6QHiLzi33eMIw4ZeU5IpcJYD38jwNUgBAHAtOSXbDWzpjSM/1hIqxuX3 iv4ZNBPqtL6Rx6YJQUgRCs//ztt/nEWROoQWl9bF//+y58UxEn2YrsDbvGx/Ddgn6DkF j3oRWubMdC/CGJ5OsSGVjnrLLtlwoyXw2G6ae90LWUFNG54R+7RVB0XZlWx/iihcnsKg KbwASgJzsFLf8CWEaeCCec70f6Ia/iL0CrSpgsrxMBKgdH+8m29InZsloNvFEbyBNWRu hECg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=C0sVaTm+B21rKUzxdJ7/QIaWSZq9jvviQexIVMnLhn4=; b=m3s+1TaT03LnxKolHjFOoX625liNpgvFmRTwGCzN0MWSc6i68vH4bvDFOMwCb7bCcB smiSdY0i0hSvpEm9ki/BUiyS6waUr228G4q/TDk3zvCPPDaburZlCraNqPARz9UtJ4aj Zr9RAAP03ue3hKpbBOxEnet1QNtT84XOunKpeYmgRIjIxBZWOIaXHQ9dr3piDuXV2lvT oCHurc2B2BqRIDMJ/muCfPrwsm1o/8Q7GBRJBcLvPsaKWXNU4dKKBQW8vlrqo0hGUe+3 4xtW0zgX4F8TGFF5qeAB0w4cgxnHAj+M0iVGfd0qRH/9PLeMFDYHjEh7cvizIwcWPW0Q ShYA== X-Gm-Message-State: AIkVDXJL019CZZcydF9BA+HjwAFPFFY0Ck6HSWMwrQsjitQkpaRvR/pxWAmGe/Bep9UIOIa2t5JBEKKKzkAUtg== X-Received: by 10.28.109.70 with SMTP id i67mr15266643wmc.102.1485816525272; Mon, 30 Jan 2017 14:48:45 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.8.194 with HTTP; Mon, 30 Jan 2017 14:48:44 -0800 (PST) In-Reply-To: <877f5c2pew.fsf@toke.dk> References: <32C42951-373F-4D90-8936-AA07039E5D73@gmail.com> <877f5c2pew.fsf@toke.dk> From: Aaron Wood Date: Mon, 30 Jan 2017 14:48:44 -0800 Message-ID: To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= Cc: Pete Heist , cake@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net Content-Type: multipart/alternative; boundary=001a11468c7e30c00b0547579e20 Subject: Re: [Cake] [Make-wifi-fast] Flent results for point-to-point Wi-Fi on LEDE/OM2P-HS available 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: Mon, 30 Jan 2017 22:48:46 -0000 --001a11468c7e30c00b0547579e20 Content-Type: text/plain; charset=UTF-8 > - Yeah, as you note Flent has a batch facility. Did you not use this > simply because you couldn't find it, or was there some other reason? > Would love some feedback on what I can do to make that more useful to > people... While I have no doubt that your 'flenter.py' works, wrapping > a wrapper in this sense makes me cringe a little bit ;) > Wait, what? It does? (I've been using wrapper scripts as well) > - Flent also has a metadata gathering feature where you can get lots of > stats from both your qdisc-based bottlenecks, and your WiFi links. > Again, it does? Neat! (I try to bury data into the tag for the run...) Question 5: For TCP you can't get packet loss from user space; you'll > need packet captures for that. So no way to get it from Flent either. > You can, however, get average throughput. Look at the box plots; if you > run multiple iterations of the same test, you can plot several data > files in a single box_combine plot, to get error bars. `flent > file.flent.gz -f summary` (which is the default if you don't specify a > plot) will get you averages per data series; or you can extract it from > the metadata. > You don't get packet loss, per se, but you can periodically poll the TCP_INFO struct via getsockopt() and get the retransmission count (which more or less gives you the packet loss rate). (which is what iperf3 does to gather stats like it's view of rtt, retransmits, etc). -Aaron --001a11468c7e30c00b0547579e20 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

=
- Yeah, as you note Flent has a batch facility. Did you not use this
=C2=A0 simply because you couldn't find it, or was there some other rea= son?
=C2=A0 Would love some feedback on what I can do to make that more useful t= o
=C2=A0 people... While I have no doubt that your 'flenter.py' works= , wrapping
=C2=A0 a wrapper in this sense makes me cringe a little bit ;)

Wait, what?=C2=A0 It does? =C2=A0(I've been usi= ng wrapper scripts as well)
=C2=A0
- Flent also has a metadata gathering feature where you can get lots of
=C2=A0 stats from both your qdisc-based bottlenecks, and your WiFi links.

Again, it does?=C2=A0 Neat! =C2=A0(I try= to bury data into the tag for the run...)=C2=A0

Question 5: For TCP you can't get packet loss = from user space; you'll
need packet captures for that. So no way to get it from Flent either.
You can, however, get average throughput. Look at the box plots; if you
run multiple iterations of the same test, you can plot several data
files in a single box_combine plot, to get error bars. `flent
file.flent.gz -f summary` (which is the default if you don't specify a<= br> plot) will get you averages per data series; or you can extract it from
the metadata.

You don't get packet = loss, per se, but you can periodically poll the TCP_INFO struct via getsock= opt() and get the retransmission count (which more or less gives you the pa= cket loss rate). =C2=A0(which is what iperf3 does to gather stats like it&#= 39;s view of rtt, retransmits, etc).

-Aaron
<= div>
--001a11468c7e30c00b0547579e20--