From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: TFRC Faster Restart implementation for Linux DCCP
Date: Thu, 26 Jul 2007 08:32:03 +0000 [thread overview]
Message-ID: <200707260932.03166@strip-the-willow> (raw)
In-Reply-To: <5640c7e00707152131k689ff53dn105ed1c0f3b90717@mail.gmail.com>
Quoting Ian McDonald:
| > | Given how TCP handle extensions I think the
| > | best way for this is a sysctl as can turn it on or off system wide.
| > | The default, initially, should be off. The other alternative is to
| > | enable it via a socket option as TCP Nagle does.
| > Could use a module parameter to the CCID3 module to enable it.
|
| I've decided to go with a socket option for now but this trivial to
| alter the code around it.
I think this is even better than a module option, since faster restart will
also affect CCID4. The problem with module options is that unloading does not
really work.
A while ago I noticed that DCCP does not support the SO_KEEPALIVE option, and the
ping probes of FR somewhat link up with this. Maybe something similar to TCP_KEEPCNT,
TCP_KEEPIDLE, TCP_KEEPINTVL is possible here?
There is an issue with the ping probes, will write up in a separate email.
next prev parent reply other threads:[~2007-07-26 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 4:31 TFRC Faster Restart implementation for Linux DCCP Ian McDonald
2007-07-16 7:51 ` [dccp] " Arjuna Sathiaseelan
2007-07-16 12:04 ` Gerrit Renker
2007-07-17 4:25 ` Ian McDonald
2007-07-17 14:38 ` Gerrit Renker
2007-07-25 9:10 ` Ian McDonald
2007-07-26 8:32 ` Gerrit Renker [this message]
2007-07-26 9:42 ` Ian McDonald
2007-07-26 10:02 ` Gerrit Renker
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=200707260932.03166@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.