From: cklatsky <notifications@github.com> To: tohojo/flent <flent@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [Flent-users] [tohojo/flent] Netperf latency stats vs ICMP (#160) Date: Fri, 10 May 2019 15:57:15 +0000 (UTC) [thread overview] Message-ID: <tohojo/flent/issues/160@github.com> (raw) [-- Attachment #1.1: Type: text/plain, Size: 293 bytes --] Hi, Do any of the supplied tests utilize netperf generated latency statistics (-j option) for the latency value? Regards, Carl -- 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/160 [-- Attachment #1.2: Type: text/html, Size: 1149 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 reply other threads:[~2019-05-10 15:58 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-10 15:57 cklatsky [this message] 2019-05-10 19:42 ` Toke Høiland-Jørgensen
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/160@github.com \ --to=notifications@github.com \ --cc=flent@noreply.github.com \ --cc=reply+AHVNJP4NV5M4ZY3WS23ZBVF24LI5XEVBNHHBUZDHXU@reply.github.com \ --cc=subscribed@noreply.github.com \ --subject='Re: [Flent-users] [tohojo/flent] Netperf latency stats vs ICMP (#160)' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox