From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Rick Jones <rick.jones2@hp.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 18:20:52 +0000 [thread overview]
Message-ID: <87bo0z15dn.fsf@toke.dk> (raw)
In-Reply-To: <529CCD6B.8000805@hp.com> (Rick Jones's message of "Mon, 02 Dec 2013 10:11:55 -0800")
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
Rick Jones <rick.jones2@hp.com> writes:
> 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.
Yeah, I was counting on that, actually. But I get your point: it's
measuring two different things. I did not have the other use case in
mind (application layer to application layer) until Lars mentioned it. I
suppose doing both would be worthwhile, and probably some of the
time-keeping logic can be reused.
Still leaves the question of whether it's possible to get to the TCP
timestamps short of sniffing the packets, though... Anyone knows?
-Toke
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-12-02 18:20 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
2013-12-02 18:20 ` Toke Høiland-Jørgensen [this message]
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=87bo0z15dn.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=rick.jones2@hp.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