All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hpe.com>
To: Dave Taht <dave.taht@gmail.com>, Roman Yeryomin <leroi.lists@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net,
	"codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
	ath10k <ath10k@lists.infradead.org>
Subject: Re: [Codel] iperf3 udp flood behavior at higher rates
Date: Mon, 2 May 2016 16:27:39 -0700	[thread overview]
Message-ID: <5727E26B.3040201@hpe.com> (raw)
In-Reply-To: <CAA93jw7uHvkKTUtXZqqWbDSWDxb=sZ+sfhdmMM1SZW3BsmZ1xA@mail.gmail.com>

On 05/02/2016 04:18 PM, Dave Taht wrote:
> Netperf does not have a multi-hop capable udp flood test (rick jones
> can explain why... )

Well, with an intro like that, how could I refuse?-)

In a nutshell, after repeated uses of the netperf UDP_STREAM test in 
non-air-gapped test setups with link up/down testing and a default route 
which pointed at the local "corporate/desktop/whathaveyou" network by QA 
engineers who should have known better, taking-out things like security 
camera video feeds, by default the data socket for a UDP_STREAM test is 
set SO_DONTROUTE.  This can be overridden with a test-specific -R 1 option.

This is not necessary if the test is UDP_RR or TCP_*.

happy benchmarking,

rick jones

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2016-05-02 23:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 23:18 iperf3 udp flood behavior at higher rates Dave Taht
2016-05-02 23:27 ` Rick Jones [this message]
2016-05-03  0:07   ` [Codel] " Dave Taht
2016-05-04  8:02 ` Roman Yeryomin
2016-05-04  8:13   ` Roman Yeryomin

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

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

  git send-email \
    --in-reply-to=5727E26B.3040201@hpe.com \
    --to=rick.jones2@hpe.com \
    --cc=ath10k@lists.infradead.org \
    --cc=codel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=leroi.lists@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.