From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] netperf-wrapper on osx?
Date: Fri, 21 Mar 2014 17:17:00 -0700 [thread overview]
Message-ID: <CALQXh-OerAT48mxBjDyCpF2pgNCMcm0sz4vWb8T2K1jRwbD9NA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw72SGoXKwrpMCw1hMh1yNL9aCRQkXCtU3ojtm4wkcDRng@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
yes. I've been meaning to write this up. here's the quick version (as
it's very late in Paris):
I followed these instructions, but ran into issues:
http://www.tschofenig.priv.at/wp/?p=963
- fping3 is needed (it's in Homebrew)
- netperf doesn't compile by default with the clang compiler, the static
inline methods need to be just static (gcc/clang incompatibility)
IIRC, that was all it took.
also, I highly recommend the head versions of both netperf and
netperf-wrapper, to get the restarting UDP ping streams. At least, if
you're on a network that's going to see some noticeable packet loss during
the initial slow-start of all the TCP loads.
-Aaron
On Fri, Mar 21, 2014 at 4:15 PM, Dave Taht <dave.taht@gmail.com> wrote:
> I am under the impression several folk here have been running the rrul
> test suite on osx. Could someone post detailed instructions on how to
> get it running? (correctly - I think fping is required for example)
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt:
> http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 2099 bytes --]
prev parent reply other threads:[~2014-03-22 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 23:15 Dave Taht
2014-03-22 0:17 ` Aaron Wood [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.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALQXh-OerAT48mxBjDyCpF2pgNCMcm0sz4vWb8T2K1jRwbD9NA@mail.gmail.com \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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