s/netperf-wrapper/Flent/g

Author: tohojo

content/cerowrt/wiki/CeroWrt_310_Release_Notes.md

@@ -273,7 +273,7 @@ default gw?
 If on the other hand, you have a jtag debugger handy, and don't have a
 iwl card on your laptop, and can look into the wifi issues, please do
 so... (all you have to do is bump up /etc/xinetd.d/netserver to 16 and
-run the netperf-wrapper against it for a few minutes)
+run the Flent against it for a few minutes)
 
 There are otherwise a huge number of interesting things that have
 accumulated for this release cycle.

content/cerowrt/wiki/Quick_Test_for_Bufferbloat.md

@@ -44,8 +44,8 @@ The Best Tests for bufferbloat:
 
 The suite of tests we developed to diagnose bufferbloat and other
 connectivity problems are good to 40GigE, but require the
-[netperf-wrapper rrul test
-suite](https://github.com/tohojo/netperf-wrapper) . Using the tools
+[Flent rrul test
+suite](https://flent.org) . Using the tools
 therein it is possible to get a good feel for how the connection is
 behaving while [you tune a shaper to fix
 it](http://snapon.lab.bufferbloat.net/~cero2/jimreisert/results.html).
@@ -94,7 +94,7 @@ Other tools for measuring network performance and latency
 4.  Both betterspeedtest.sh and netperfrunner.sh use the
     [**netperf**](http://netperf.org/netperf/) program (built
     into CeroWrt) to drive traffic to see its performance.
-5.  [**netperf-wrapper**](https://github.com/tohojo/netperf-wrapper) is
+5.  [**Flent**](https://flent.org) is
     a handy tool for running the RRUL test and producing attractive
     graphs of the results. (RRUL specifies that multiple netperf
     sessions run simultaneously to heavily load the network in

content/codel/wiki/Benchmarking_Codel_and_FQ_Codel.md

@@ -24,7 +24,7 @@ WHILE doing a ping. A netperf, WHILE making a phone call, trying to hold
 the latency and jitter of the smaller stream (ping or voip)small.
 
 We have developed the
-[netperf-wrapper](https://github.com/tohojo/netperf-wrapper) tool suite
+[Flent](https://flent.org) tool suite
 to make benchmarking these various network attributes easier, with
 results that can be easily shared and graphed several dozen ways. It is
 available for Linux, BSD, and BSD-derived systems such as OSX.

content/codel/wiki/Cake.md

@@ -378,7 +378,7 @@ Some example results while a rrul test was running:
       drops          173          21           0           0
       marks            0           0           0           0
 
-A problem I have is in reconciling the netperf-wrapper plots which hit a
+A problem I have is in reconciling the Flent plots which hit a
 minimum of 2ms for sparse flows, where I typically see \~200us delay in
 the qdiscs themselves. I have generally not cared at all about about
 anything less than 3ms prior to now.

content/codel/wiki/RRUL_test_suite.md

@@ -23,7 +23,7 @@ RRUL prototype
 --------------
 
 A rrul prototype is being developed as part of the
-[netperf-wrappers](https://github.com/tohojo/netperf-wrapper) tests. As
+[Flent](https://flent.org) tests. As
 the title suggests, the tests are being wrapped around the popular
 [netperf](http://www.netperf.org) netperf network analysis tool.
 Requirements are a recent version of netperf, python, matplotlib,

content/make-wifi-fast/wiki/Wifi_Stack_Rework.md

@@ -142,7 +142,7 @@ and so on.
 Better Benchmarks and tools
 ---------------------------
 
-Leveraging the netperf-wrapper test suite, we hope to encourage industry
+Leveraging the Flent test suite, we hope to encourage industry
 and users to look at the real problems of wifi on voip,
 videoconferencing, gaming, and web traffic. There are other benchmarks
 being developed that look hard at the problems in bursty traffic as