From: Jonathan Morton <chromatix99@gmail.com>
To: divya singla <divyasingla1989@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] Latency vs Delay
Date: Sat, 14 Mar 2015 16:57:06 +0200 [thread overview]
Message-ID: <CAJq5cE3V+9W0bEYfaVE1u7zpBZJjvm1V-mnpFaKV3JavNNiiwg@mail.gmail.com> (raw)
In-Reply-To: <CAONkte9rz_QAE0-BP-3mJ4aZ5KysMSF5hOK2eat+0YjHx3xyxA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 303 bytes --]
They mean the same thing, for most practical purposes. However, you could
(when writing your own papers) usefully define latency as the total RTT,
and delay as only the avoidable components of that. The speed of light,
etc, mean that some latency is unavoidable in any communication.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 345 bytes --]
next prev parent reply other threads:[~2015-03-14 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 14:53 divya singla
2015-03-14 14:57 ` Jonathan Morton [this message]
[not found] <mailman.1.1426359602.27522.codel@lists.bufferbloat.net>
2015-03-15 2:05 ` David Collier-Brown
2015-03-16 0:42 ` David Collier-Brown
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=CAJq5cE3V+9W0bEYfaVE1u7zpBZJjvm1V-mnpFaKV3JavNNiiwg@mail.gmail.com \
--to=chromatix99@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=divyasingla1989@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