Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	"Eggert, Lars" <lars@netapp.com>
Cc: "bloat-devel@lists.bufferbloat.net" <bloat-devel@lists.bufferbloat.net>
Subject: Re: One-way delay measurement for netperf-wrapper
Date: Mon, 02 Dec 2013 10:11:55 -0800	[thread overview]
Message-ID: <529CCD6B.8000805@hp.com> (raw)
In-Reply-To: <87mwknk0hw.fsf@toke.dk>

On 11/29/2013 01:42 AM, Toke Høiland-Jørgensen wrote:
> Well, what the LINCS people have done (the link in my previous mail) is
> basically this: Sniff TCP packets that have timestamps on them (i.e.
> with the TCP timestamp option enabled), and compute the delta between
> the timestamps as a latency measure. Now this only gives an absolute
> latency measure if the clocks are synchronised; however, if we're
> interested in measuring queueing latency, i.e. induced *extra* latency,
> this can be calculated as (latency - min-latency) where min-latency is
> the minimum observed latency throughout the lifetime of the connection
> (this is the same mechanism LEDBAT uses, btw).

Those TCP timestamps are generated (iirc) when TCP transmits the data, 
not when the application presents the data to TCP.  Not a deal breaker 
necessarily, but something to keep in mind.

rick jones

  parent reply	other threads:[~2013-12-02 18:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28 18:51 Toke Høiland-Jørgensen
2013-11-29  8:45 ` Eggert, Lars
2013-11-29  9:42   ` Toke Høiland-Jørgensen
2013-11-29 10:20     ` Eggert, Lars
2013-11-29 13:04       ` Toke Høiland-Jørgensen
2013-11-29 14:30         ` Eggert, Lars
2013-11-29 16:55           ` Dave Taht
2013-12-02 18:11     ` Rick Jones [this message]
2013-12-02 18:20       ` Toke Høiland-Jørgensen
2013-11-28 20:30 Hal Murray
2013-12-02  5:45 Hal Murray
2013-12-02  8:34 ` Toke Høiland-Jørgensen

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=529CCD6B.8000805@hp.com \
    --to=rick.jones2@hp.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=lars@netapp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox