From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 1/6]: Avoid accumulation of large send credit
Date: Sat, 16 Jun 2007 14:41:06 +0000 [thread overview]
Message-ID: <200706161541.06386@strip-the-willow> (raw)
In-Reply-To: <200706091957.56966@strip-the-willow>
| Agree with Gerrit's comments in patchset description that there is
| still discussion around this. Still doing something is better than
| doing nothing.
Also agree with what you are saying. This is really why I would like
to get the experimental test tree for DCCP/CCID3 started soon.
With the mechanism already in place, it is a trivial change to use
a different value.
Kohler/Floyd currently suggest to use 1 RTT, which derives from the theory of TFRC.
The value t_ipi derives from the way the packets are currently scheduled.
Neither value may be the last piece of wisdom - we need people testing
this and report their experience + suggestions.
prev parent reply other threads:[~2007-06-16 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 18:57 [PATCH 1/6]: Avoid accumulation of large send credit Gerrit Renker
2007-06-16 5:10 ` Ian McDonald
2007-06-16 14:41 ` Gerrit Renker [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200706161541.06386@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