Flent-users discussion archives
 help / color / mirror / Atom feed
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] Force Iperf test instead netperf? (#161)
Date: Mon, 20 May 2019 09:33:23 -0700	[thread overview]
Message-ID: <tohojo/flent/issues/161/494060960@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/161@github.com>


[-- Attachment #1.1: Type: text/plain, Size: 840 bytes --]

acdcjavier <notifications@github.com> writes:

> Hello
> Is it possible to force Iperf testing instead netperf?
>
> I need to make some thoughtput test in my LAN configuration, but
> netperf is older and Iperf is more compatible with Linux/windows.

Not generally, no. Netperf has quite a few options that iperf lacks, and
it's the tried and true solution on Linux, so that is the primary
supported tool. I have thought about restructuring things to allow a
fallback, but it's not trivial, so that hasn't materialised yet.

You're right that netperf is a bit iffy on Windows, though... one
work-around may be to use WSL if you can't use a Linux box...


-- 
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/161#issuecomment-494060960

[-- Attachment #1.2: Type: text/html, Size: 2298 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

      reply	other threads:[~2019-05-20 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 14:00 acdcjavier
2019-05-20 16:33 ` Toke Høiland-Jørgensen [this message]

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/161/494060960@github.com \
    --to=notifications@github.com \
    --cc=flent@noreply.github.com \
    --cc=reply+AHVNJP2OIILN5VME6Q3RTBF26AEVHEVBNHHBVF3ZJA@reply.github.com \
    --cc=subscribed@noreply.github.com \
    --subject='Re: [Flent-users] [tohojo/flent] Force Iperf test instead netperf? (#161)' \
    /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