Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Bob McMahon <bob.mcmahon@broadcom.com>
Cc: David Reed <dpreed@reed.com>,
	make-wifi-fast@lists.bufferbloat.net,
	Johannes Berg <johannes@sipsolutions.net>,
	brouer@redhat.com
Subject: Re: [Make-wifi-fast] less latency, more filling... for wifi
Date: Wed, 11 Oct 2017 23:30:56 +0200	[thread overview]
Message-ID: <20171011233056.3634daea@redhat.com> (raw)
In-Reply-To: <CAHb6LvrWKyWLezDFJkLFe8C9Dm67ko0H0WoYFXoJGpjQ-EjZ3Q@mail.gmail.com>

Hi Bob,

Just wanted to let you know, that after you posted this, I've started
to use your iperf2 tool again.  To verify some of my kernel code.

I particularly liked that I can send with a specific PPS rate, like:

 iperf2-git -c 172.16.0.2 -e -u -b 20000pps -i 1


On Mon, 9 Oct 2017 14:04:35 -0700 Bob McMahon <bob.mcmahon@broadcom.com> wrote:

> Not sure if this is helpful but we've added end/end latency measurements
> for UDP traffic in iperf 2.0.10 <https://sourceforge.net/projects/iperf2/>.

I tried it out, but the clock between my two machines are not accurate
enough (as you hint below).

>   It does require the clocks to be synched.  I use a spectracom tsync pcie
> card with either an oven controlled oscillator or a GPS disciplined one,
> then use precision time protocol to distribute the clock over ip
> multicast.  

> For Linux, the traffic threads are set to realtime scheduling
> to minimize latency adds per thread scheduling..

If I use the --realtime option, I did run into issues where the server
thread would busypoll 100% after e.g. a client stopped a test prematurely.
And I had to kill it with -9.

Thanks for you work!
-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer

  parent reply	other threads:[~2017-10-11 21:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 20:13 Dave Taht
2017-10-09 20:41 ` dpreed
2017-10-09 21:04   ` Bob McMahon
2017-10-09 21:44     ` Simon Barber
2017-10-09 22:02       ` Bob McMahon
2017-10-11 20:03         ` Bob McMahon
2017-10-16 21:26       ` Simon Barber
2017-10-17  4:53         ` Bob McMahon
2017-10-11 21:30     ` Jesper Dangaard Brouer [this message]
2017-10-12  8:32       ` Toke Høiland-Jørgensen
2017-10-12 18:51         ` Bob McMahon
2017-10-13  9:28           ` Toke Høiland-Jørgensen
2017-10-13 18:47             ` Bob McMahon
2017-10-13 19:41               ` Bob McMahon
2017-10-14  1:46                 ` Bob McMahon
     [not found] <mailman.778.1507581712.3609.make-wifi-fast@lists.bufferbloat.net>
2017-10-16 18:28 ` Pete Heist
2017-10-16 19:56   ` Dave Taht

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/make-wifi-fast.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171011233056.3634daea@redhat.com \
    --to=brouer@redhat.com \
    --cc=bob.mcmahon@broadcom.com \
    --cc=dpreed@reed.com \
    --cc=johannes@sipsolutions.net \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    /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