From: "Dave Täht" <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [Flent-users] [tohojo/flent] udp_rtt in more tests (#230)
Date: Sun, 27 Jun 2021 10:40:10 -0700 [thread overview]
Message-ID: <tohojo/flent/issues/230@github.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
Since ping is being spoofed by starlink, a udp ping test in combination with tcp_nup/tcp_ndown or appears needed.
also I am loving sampling things at a 3ms interval in irtt general.
I think a new generation of tests is needed. rrulv2 ?
I am thinking nup and ndown would be good names for something that leveraged irtt, but I am not sure how using a much smaller interval than socket-stats for irtt could work.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/230
[-- Attachment #2: Type: text/html, Size: 1439 bytes --]
next reply other threads:[~2021-06-27 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 17:40 Dave Täht [this message]
2021-06-27 17:40 ` [Flent-users] " Dave Täht
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.flent.org/postorius/lists/flent-users.flent.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tohojo/flent/issues/230@github.com \
--to=notifications@github.com \
--cc=flent@noreply.github.com \
--cc=reply+AHVNJPYPS2VJON4ESDPLITF64SMPVEVBNHHDO7NNA4@reply.github.com \
--cc=subscribed@noreply.github.com \
/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