From: dave seddon <dave.seddon.ca@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] some comprehensive arm64 w/cake results
Date: Fri, 13 Oct 2023 10:25:39 -0700 [thread overview]
Message-ID: <CANypexS=7eP0eU4xTO62swRp2o+fM0rg4rG0OSMqq6ybKx2omA@mail.gmail.com> (raw)
In-Reply-To: <CANypexR9-Cpxup83w9tgcer7Dv48Hsun6+JR=qLPAdhhnRP58w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4165 bytes --]
My bad. There's a bug for this.... Looks like I have to downgrade fping
https://github.com/tohojo/flent/issues/232
https://github.com/schweikert/fping/issues/203
On Fri, Oct 13, 2023 at 8:59 AM dave seddon <dave.seddon.ca@gmail.com>
wrote:
> G'day,
>
> I've been working away on automation of the tests. Pretty close to having
> much nicer tests with a lot more details. I've also got the risc-v device
> working.
>
> However, I've run into something funny with flent. Flent is not happy
> with fping or ping.
>
> das@3rd:~/Downloads/cake/cmd/run_qdiscs_tests$ /usr/bin/sudo /usr/sbin/ip
> netns exec network101 /usr/bin/flent rrul --output
> /tmp/qdisc/2023-10-13T15:53:21/pi4/noqueue/flent/test/15_flent/flent_pi4_noqueue.png
> --data-dir /tmp/qdisc/2023-10-13T15:53:21/pi4/noqueue/flent/test/15_flent/
> --format summary --plot all_scaled --title-extra
> 2023-10-13T15:53:21_pi4_noqueue --note 2023-10-13T15:53:21_pi4_noqueue
> --extended-metadata --host 172.17.51.10 --length 60 --ipv4 --socket-stats
> Starting Flent 2.0.1 using Python 3.10.12.
> Starting rrul test. Expected run time: 70 seconds.
> WARNING: Found fping, but couldn't parse its output. Not
> using. <---------------- ???
> ERROR: Runner Ping (ms) ICMP failed check: Cannot parse output of the
> system ping binary (/usr/bin/ping). Please install fping v3.5+. <----- ??
>
> das@3rd:~/Downloads/cake/cmd/run_qdiscs_tests$ dpkg --list | grep ping
> ii fping 5.1-1
> amd64 sends ICMP ECHO_REQUEST packets to network hosts
> ii iputils-ping 3:20211215-1
> amd64 Tools to test the reachability of network hosts
> ii kpartx 0.8.8-1ubuntu1.22.04.1
> amd64 create device mappings for partitions
> ii libharfbuzz0b:amd64 2.7.4-1ubuntu3.1
> amd64 OpenType text shaping engine (shared library)
> das@3rd:~/Downloads/cake/cmd/run_qdiscs_tests$ fping --version
> fping: Version 5.1
> das@3rd:~/Downloads/cake/cmd/run_qdiscs_tests$ ping -V
> ping from iputils 20211215
>
> das@3rd:~/Downloads/cake/cmd/run_qdiscs_tests$ cat /etc/lsb-release
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=22.04
> DISTRIB_CODENAME=jammy
> DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"
>
> I did install via "apt install fping"
>
> Any thoughts please?
>
> Kind regards,
> Dave
>
> On Thu, Sep 28, 2023 at 6:27 AM Sebastian Moeller via Cake <
> cake@lists.bufferbloat.net> wrote:
>
>>
>>
>> > On Sep 28, 2023, at 15:19, David Lang <david@lang.hm> wrote:
>> >
>> > On Thu, 28 Sep 2023, Sebastian Moeller via Cake wrote:
>> >
>> >> P.S.: I am tempted, but will likely wait until they are available in
>> quantity and hope that the street price comes down a bit before getting one
>> ;)
>> >
>> > They aren't available at all yet, and it's not clear when they will be
>> available.
>>
>> The announcement was end of October, but I think I could
>> pre-order right now if I was feeling an urge. You are right though,
>> announced != available or delivered.
>>
>> Regards
>> Sebastian
>>
>> P.S.: I have a pi400 in use as "desktop" for my oldest kid, this is close
>> to be actually generally usable, I would guess that changing a potential
>> p500 from the pi400's 4GB to 8 GB together with the other imprivements the
>> 5 brings might push it over the threshold into the truly useful category.
>> Which probably means that either a potential pi500 will come late and
>> probably with only 4 GB, but let's see how this works out now that the
>> supply situation is less problematic.
>> And I understand that there are other capable ARM based SoCs for
>> homerouter/desktop duty, I just happen ot have a soft spot for the
>> raspberry project ;)
>>
>> >
>> > David Lang
>>
>> _______________________________________________
>> Cake mailing list
>> Cake@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cake
>>
>
>
> --
> Regards,
> Dave Seddon
> +1 415 857 5102
>
--
Regards,
Dave Seddon
+1 415 857 5102
[-- Attachment #2: Type: text/html, Size: 5976 bytes --]
next prev parent reply other threads:[~2023-10-13 17:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 1:05 Dave Taht
2023-09-18 1:25 ` Jonathan Morton
2023-09-18 16:57 ` David P. Reed
2023-09-18 19:50 ` dave seddon
2023-09-18 20:24 ` David P. Reed
2023-09-18 22:07 ` Jonathan Morton
2023-09-28 11:44 ` Jonathan Morton
2023-09-28 12:15 ` Sebastian Moeller
2023-09-28 12:33 ` Jonathan Morton
2023-09-28 12:56 ` David Lang
2023-09-28 13:08 ` Sebastian Moeller
2023-09-28 13:19 ` David Lang
2023-09-28 13:27 ` Sebastian Moeller
2023-10-13 15:59 ` dave seddon
2023-10-13 17:25 ` dave seddon [this message]
2023-10-15 15:11 ` dave seddon
2023-10-15 15:52 ` Sebastian Moeller
2023-10-15 16:24 ` dave seddon
2023-10-15 20:29 ` David P. Reed
2023-10-16 3:52 ` Jonathan Morton
2023-10-15 15:53 ` Dave Taht
2023-10-23 20:31 ` dave seddon
2023-10-23 20:35 ` dave seddon
2023-10-24 16:27 ` dave seddon
2023-10-24 21:35 ` dave seddon
2023-10-24 22:06 ` Dave Taht
2023-09-18 22:13 ` Jonathan Morton
2023-09-18 22:52 ` dave seddon
2023-09-18 23:08 ` Jonathan Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANypexS=7eP0eU4xTO62swRp2o+fM0rg4rG0OSMqq6ybKx2omA@mail.gmail.com' \
--to=dave.seddon.ca@gmail.com \
--cc=cake@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox