From: "Toke Høiland-Jørgensen" <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [Flent-users] [tohojo/flent] Two latency measurement flows with different tos byte for each? (#169)
Date: Mon, 22 Jul 2019 04:50:06 -0700 [thread overview]
Message-ID: <tohojo/flent/issues/169/513759133@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/169@github.com>
[-- Attachment #1.1: Type: text/plain, Size: 592 bytes --]
Pete Heist <notifications@github.com> writes:
> Is there a way I could start two latency measurement flows, either
> both ICMP or both UDP (ideally it should be the same), each of which
> has a different value for the tos field, alongside the tcp_nup test?
See 878f297cd336539189fe577ea82c1037ed136b20 which adds the
ping_markings test parameter; you can add extra ping flows and set their
markings...
--
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/169#issuecomment-513759133
[-- Attachment #1.2: Type: text/html, Size: 2000 bytes --]
[-- Attachment #2: Type: text/plain, Size: 151 bytes --]
_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org
next prev parent reply other threads:[~2019-07-22 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 10:35 Pete Heist
2019-07-22 11:50 ` Toke Høiland-Jørgensen [this message]
2019-07-22 14:29 ` Pete Heist
2019-07-22 14:29 ` Pete Heist
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/169/513759133@github.com \
--to=notifications@github.com \
--cc=flent@noreply.github.com \
--cc=reply+AHVNJP3UCTR5AC6AIQZNGH53ILKW5EVBNHHBYEZQ5Y@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