All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Dave Taht <dave.taht@gmail.com>, Eric Dumazet <eric.dumazet@gmail.com>
Cc: "Tom Herbert" <therbert@google.com>,
	"Jesper Dangaard Brouer" <brouer@redhat.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Stephen Hemminger" <stephen@networkplumber.org>,
	"David Miller" <davem@davemloft.net>,
	"Hannes Frederic Sowa" <hannes@stressinduktion.org>,
	"Daniel Borkmann" <dborkman@redhat.com>,
	"Florian Westphal" <fw@strlen.de>,
	"Toke Høiland-Jørgensen" <toke@toke.dk>,
	"Tim Shepard" <shep@alum.mit.edu>,
	"Avery Pennarun" <apenwarr@google.com>
Subject: Re: Qdisc: Measuring Head-of-Line blocking with netperf-wrapper
Date: Mon, 15 Sep 2014 12:12:24 -0700	[thread overview]
Message-ID: <54173A18.2010705@hp.com> (raw)
In-Reply-To: <CAA93jw7ZNbvwLtcFfwRVVF8asnxwp104g7iR-oZv3nj0mqKbOQ@mail.gmail.com>

On 09/15/2014 11:55 AM, Dave Taht wrote:
> Problems with TCP_RR and UDP_RR are that they are subject to a RTO on
> packet loss.

One possible way to work/kludge around that for TCP_RR would be to have 
a burst-mode test with say five or so transactions in flight at one 
time.  That then should allow for fast retrans on the occasional 
single-packet loss and it will be just an RTT rather than an RTO.  There 
would probably be some interactions with cwnd and bundling though upon 
that retransmission, even with -D set.

> It would be nice if netperf could sprout a "send a user specified
> packet size on this isochronous interval (with a resolution below a
> ms) over X transport" test. Or there was something simpler than owamp
> but as secure.

If you are willing to let netperf spin (ie burn local CPU on the system 
on which netperf is running) over the interval you can configure 
--enable-intervals --enable-spin  and then it will spin rather than rely 
on the resolution of setitimer().  Then the command line would be 
something along the lines of:

netperf -H <destination> -b 1 -w <waittime> -- -m <size>

and it will then make one send of <size> every <waittime>.

happy benchmarking,

rick

  reply	other threads:[~2014-09-15 19:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 16:45 Qdisc: Measuring Head-of-Line blocking with netperf-wrapper Jesper Dangaard Brouer
2014-09-15 17:10 ` Tom Herbert
2014-09-15 17:24   ` Eric Dumazet
2014-09-15 18:55     ` Dave Taht
2014-09-15 19:12       ` Rick Jones [this message]
2014-09-16  6:30     ` Jesper Dangaard Brouer
2014-09-16 15:52       ` Tom Herbert
2014-09-16 13:22 ` Jesper Dangaard Brouer
2014-09-16 13:59   ` Eric Dumazet
2014-09-16 15:56     ` Jesper Dangaard Brouer
2014-09-16 16:08       ` Dave Taht
2014-09-16 16:30       ` Eric Dumazet
2014-09-17  7:39         ` Jesper Dangaard Brouer

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=54173A18.2010705@hp.com \
    --to=rick.jones2@hp.com \
    --cc=apenwarr@google.com \
    --cc=brouer@redhat.com \
    --cc=dave.taht@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=eric.dumazet@gmail.com \
    --cc=fw@strlen.de \
    --cc=hannes@stressinduktion.org \
    --cc=netdev@vger.kernel.org \
    --cc=shep@alum.mit.edu \
    --cc=stephen@networkplumber.org \
    --cc=therbert@google.com \
    --cc=toke@toke.dk \
    /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.