From: Jonathan Morton <chromatix99@gmail.com>
To: Noah Causin <n0manletter@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] best way at getting at tcp ack data?
Date: Wed, 4 Oct 2017 06:22:05 +0300 [thread overview]
Message-ID: <CAJq5cE3hVX+uifcwZuHT9+hDybjqCxEkPnCr=vyrUwSBUwOrWw@mail.gmail.com> (raw)
In-Reply-To: <198aa7d2-246d-40c2-fd46-89979fa249d4@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 175 bytes --]
No, because acks are cumulative. Dropping an ack doesn't normally trigger
any retransmissions, and is actually difficult to detect reliably at the
sender.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 222 bytes --]
next prev parent reply other threads:[~2017-10-04 3:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 3:10 Dave Taht
2017-10-01 5:22 ` Jonathan Morton
2017-10-01 5:25 ` Dave Taht
2017-10-02 1:08 ` Jonathan Morton
2017-10-02 2:40 ` Dave Taht
2017-10-04 3:17 ` Noah Causin
2017-10-04 3:22 ` Jonathan Morton [this message]
2017-10-04 3:23 ` Jonathan Morton
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='CAJq5cE3hVX+uifcwZuHT9+hDybjqCxEkPnCr=vyrUwSBUwOrWw@mail.gmail.com' \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=n0manletter@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