From: hiren panchasara <hiren@strugglingcoder.info>
To: netdev@vger.kernel.org
Subject: A TLP implementation question
Date: Tue, 13 Feb 2018 16:27:51 -0800 [thread overview]
Message-ID: <20180214002751.GF28312@strugglingcoder.info> (raw)
[-- Attachment #1: Type: text/plain, Size: 641 bytes --]
Looking at current net-next to understand an aspect of TLP (tail loss
probe) implementation.
https://tools.ietf.org/html/draft-ietf-tcpm-rack-02 is the source of
truth now for TLP and 6.2.1. Phase 1: Scheduling a loss probe
Step 1: Check conditions for scheduling a PTO. has following as one of
the conditions:
(d) The most recently transmitted data was not itself a TLP probe
(i.e. a sender MUST NOT send consecutive TLP probes)
I would appreciate if someone can help me trace how current code is
trying to enforce this requirement. How does it check/track that the
last (re)transmitted packet was a tlp probe.
Thanks in advance,
Hiren
[-- Attachment #2: Type: application/pgp-signature, Size: 603 bytes --]
next reply other threads:[~2018-02-14 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 0:27 hiren panchasara [this message]
2018-02-14 1:11 ` A TLP implementation question Yuchung Cheng
2018-02-14 7:39 ` hiren panchasara
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=20180214002751.GF28312@strugglingcoder.info \
--to=hiren@strugglingcoder.info \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).