From: "Toke Høiland-Jørgensen" <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: flent-users <flent-users@flent.org>,
Comment <comment@noreply.github.com>
Subject: [Flent-users] Re: [tohojo/flent] rrul tests are not being able to saturate link (#218)
Date: Thu, 17 Dec 2020 15:13:34 -0800 [thread overview]
Message-ID: <tohojo/flent/issues/218/747763365@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/218@github.com>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
olg33 <notifications@github.com> writes:
> In a related issue, It took our attention that whenever we run a rrul or rrul_var test, upload traffic seems to be absent.
>
> Below examples were performed with two servers connected back-to-back
> with no router in between to rule out any blockage (they connect using
> an ethernet switch with ports in the same Vlan).
Erm, that does sound odd! Only obvious thing I can immediately think of
is maybe the network card is running in half-duplex mode? Did you check
the output of ethtool for the interface you're using?
Otherwise, to debug further you can try running with -L and looking at
the netperf output in the log file to see if there's any obvious
pointers there...
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/218#issuecomment-747763365
[-- Attachment #2: Type: text/html, Size: 1870 bytes --]
next prev parent reply other threads:[~2020-12-17 23:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 0:12 [Flent-users] " olg33
2020-12-15 11:37 ` [Flent-users] " Toke Høiland-Jørgensen
2020-12-15 22:19 ` olg33
2020-12-17 23:01 ` olg33
2020-12-17 23:13 ` Toke Høiland-Jørgensen [this message]
2020-12-18 17:45 ` olg33
2021-01-13 17:24 ` 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/218/747763365@github.com \
--to=notifications@github.com \
--cc=comment@noreply.github.com \
--cc=flent-users@flent.org \
--cc=flent@noreply.github.com \
--cc=reply+AHVNJP2MJPSPWEH7MFWEUDN547DR5EVBNHHC3OAZRU@reply.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