From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dong Mo <montedong@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] New to codel-- how to run codel on a linux box?
Date: Thu, 05 Dec 2013 23:43:27 +0000 [thread overview]
Message-ID: <878uvyc19c.fsf@toke.dk> (raw)
In-Reply-To: <CAAUsAoR5GvMLO5tR420McXXBd+LmMJy2EnqZZxGkzdUi0OFPzg@mail.gmail.com> (Dong Mo's message of "Thu, 5 Dec 2013 17:28:44 -0600")
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
Dong Mo <montedong@gmail.com> writes:
> Thanks. My problem is solved.
Excellent. Do share your results :)
> It seems to me paping can sample for the RTT over this particular port, not the
> whole connection setup time. Maybe it only record for the sync time but I am not
> fully sure. From the latency result, it is quite close to RTT of the
> link.
Well, looking at the source code it seems to do a new connection each
time:
https://code.google.com/p/paping/source/browse/trunk/src/main.cpp#80
and
https://code.google.com/p/paping/source/browse/trunk/src/socket.cpp#106
It seems to call connect(), then measure the time until select() returns
with the socket ready to either read or write. Not sure when Linux
considers a TCP socket to be ready, but I guess it's probably after
receiving the SYN+ACK of connection setup, which would be one RTT after
calling connect(), and would fit with what you're seeing. :)
-Toke
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]
prev parent reply other threads:[~2013-12-05 23:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 5:04 Dong Mo
2013-11-23 10:23 ` Jonathan Morton
2013-11-23 14:43 ` Dave Taht
2013-12-05 19:36 ` Dong Mo
2013-12-05 19:49 ` Dong Mo
2013-12-05 20:06 ` Jonathan Morton
2013-12-05 20:21 ` Dong Mo
2013-12-05 21:03 ` Toke Høiland-Jørgensen
2013-12-05 22:29 ` Dong Mo
2013-12-05 23:25 ` Toke Høiland-Jørgensen
2013-12-05 23:28 ` Dong Mo
2013-12-05 23:43 ` Toke Høiland-Jørgensen [this message]
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878uvyc19c.fsf@toke.dk \
--to=toke@toke.dk \
--cc=codel@lists.bufferbloat.net \
--cc=montedong@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