From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 2/6]: Simplify control flow in the calculation of t_ipi
Date: Mon, 27 Nov 2006 12:31:20 +0000 [thread overview]
Message-ID: <200611271231.20662@strip-the-willow> (raw)
In-Reply-To: <200611211545.18544@strip-the-willow>
| > [CCID 3]: Simplify control flow in the calculation of t_ipi
<snip>
| > In addition, a problematic comment in ccid3_calc_new_t_ipi() was removed:
| > * the first part of the comment (initial t_ipi = 1 second) is correct
| > * the second part of the comment is not correct wrt. [RFC 3448, 4.4]
|
| Why is the second part of the comment wrong?
|
| RFC 3448, 4.4:
|
| 4.4. Expiration of nofeedback timer
|
| If the nofeedback timer expires, the sender should perform the
| following actions:
|
| 1) Cut the sending rate in half. If the sender has received feedback
| from the receiver, this is done by modifying the sender's cached
| copy of X_recv (the receive rate). Because the sending rate is
| limited to at most twice X_recv, modifying X_recv limits the
| current sending rate, but allows the sender to slow-start,
| doubling its sending rate each RTT, if feedback messages resume
| reporting no losses.
|
| If the sending rate is halved, doesn't it implies the inter packet
| interval is doubled?
Yes that is right. Ian, I apologise - you were correct in this comment.
Will re-send an update.
next prev parent reply other threads:[~2006-11-27 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 15:45 [PATCH 2/6]: Simplify control flow in the calculation of t_ipi Gerrit Renker
2006-11-26 17:10 ` Arnaldo Carvalho de Melo
2006-11-26 17:37 ` Arnaldo Carvalho de Melo
2006-11-27 12:31 ` Gerrit Renker [this message]
2006-11-27 12:34 ` Gerrit Renker
2006-11-27 13:48 ` Arnaldo Carvalho de Melo
2006-11-27 13:56 ` Gerrit Renker
2006-11-27 19:15 ` Ian McDonald
2006-11-27 19:21 ` Arnaldo Carvalho de Melo
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=200611271231.20662@strip-the-willow \
--to=gerrit@erg.abdn.ac.uk \
--cc=dccp@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