Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "Eggert, Lars" <lars@netapp.com>
Cc: "Klatsky, Carl" <Carl_Klatsky@cable.comcast.com>,
	"cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>,
	Aaron Wood <woody77@gmail.com>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>,
	Greg White <g.white@cablelabs.com>
Subject: Re: [Cake] [Cerowrt-devel] [Bloat] heisenbug: dslreports 16 flow test vs	cablemodems
Date: Fri, 15 May 2015 10:55:32 +0200	[thread overview]
Message-ID: <DF86DC46-FCB9-40B4-840B-F0CD8F7895DD@gmx.de> (raw)
In-Reply-To: <8C015B1B-EFBA-4647-AD83-BAFDD16A4AF2@netapp.com>

Hi Lars,


On May 15, 2015, at 10:18 , Eggert, Lars <lars@netapp.com> wrote:

> On 2015-5-15, at 06:44, Aaron Wood <woody77@gmail.com> wrote:
>> ICMP prioritization over TCP?
> 
> Probably.

	Interesting so far I often heard ICMP echo requests are bad as they are often rate-limited and/or processed in a slow path in routers...

> 
> Ping in parallel to TCP is a hacky way to measure latencies; not only because of prioritization, but also because you don't measure TCP send/receive buffer latencies (and they can be large, auto-tuning is not so great.)

	I guess the concurrent ICMP echo requests are a better measure for flow separation and sparse-flow-boostiing than inter-flow latency. TCP embedded timestamps would be a jacky way to measure those ;) . 

> 
> You really need to embed timestamps in the TCP bytestream and echo them back. See the recent netperf patch I sent.

	I hope this makes into the main netperf branch…

Best Regards
	Sebastian

> 
> Lars
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


  reply	other threads:[~2015-05-15  8:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 19:13 [Cake] " Dave Taht
2015-05-15  2:48 ` Greg White
2015-05-15  4:44   ` [Cake] [Cerowrt-devel] " Aaron Wood
2015-05-15  8:18     ` [Cake] [Bloat] " Eggert, Lars
2015-05-15  8:55       ` Sebastian Moeller [this message]
2015-05-15 11:10         ` [Cake] [Cerowrt-devel] [Bloat] " Alan Jenkins
2015-05-15 11:27       ` [Cake] [Bloat] [Cerowrt-devel] " Bill Ver Steeg (versteb)
2015-05-15 12:19         ` [Cake] [Cerowrt-devel] [Bloat] " Jonathan Morton
2015-05-15 12:44         ` [Cake] [Bloat] [Cerowrt-devel] " Eggert, Lars
2015-05-15 13:09           ` Bill Ver Steeg (versteb)
2015-05-15 13:35             ` Jim Gettys
2015-05-15 14:36               ` Simon Barber
2015-05-18  3:30                 ` [Cake] [Cerowrt-devel] [Bloat] " dpreed
2015-05-18  5:06                   ` Simon Barber
2015-05-18  9:06                     ` Bill Ver Steeg (versteb)
2015-05-18 11:42                     ` [Cake] [Bloat] [Cerowrt-devel] " Eggert, Lars
2015-05-18 11:57                       ` luca.muscariello
2015-05-18 12:30                       ` Simon Barber
2015-05-18 15:03                         ` Jonathan Morton
2015-05-18 15:09                         ` dpreed
2015-05-18 15:32                           ` Simon Barber
2015-05-18 17:21                             ` Dave Taht
2015-05-18 15:40                           ` Jonathan Morton
2015-05-18 17:03                             ` [Cake] [Cerowrt-devel] [Bloat] " Sebastian Moeller
2015-05-18 17:17                               ` Jonathan Morton
2015-05-18 18:14                                 ` Sebastian Moeller
2015-05-18 18:37                                   ` [Cake] [Bloat] [Cerowrt-devel] " Dave Taht
2015-05-19 16:25                           ` Sebastian Moeller
2015-05-19 16:58                           ` Alan Jenkins
2015-05-15 16:59               ` [Cake] [Cerowrt-devel] [Bloat] " Dave Taht
2015-05-15 17:47   ` [Cake] " 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/cake.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=DF86DC46-FCB9-40B4-840B-F0CD8F7895DD@gmx.de \
    --to=moeller0@gmx.de \
    --cc=Carl_Klatsky@cable.comcast.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=g.white@cablelabs.com \
    --cc=lars@netapp.com \
    --cc=woody77@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