From: Werner Almesberger <wa@almesberger.net>
To: netdev@oss.sgi.com
Subject: TCP connection passing, version 2
Date: Thu, 31 Oct 2002 20:00:17 -0300 [thread overview]
Message-ID: <20021031200017.A21544@almesberger.net> (raw)
In-Reply-To: <20021031045909.A15756@almesberger.net>; from wa@almesberger.net on Thu, Oct 31, 2002 at 04:59:09AM -0300
Another update:
http://www.almesberger.net/tcpcp/tcpcp-2.tar.gz
This one fixes window, MSS, and buffer space handling. I've also
added a bit of documentation describing how to use it properly.
- Werner
----------------------------------- CHANGES -----------------------------------
Version 2 (31-OCT-2002)
-----------------------
- removed 1000 "voodoo slack" term in __tcpcp_maxicisize's size estimate
- tcpcp.c:tcpcp_init now correctly identifies the version as the one of the ICI
format, not as the one of tcpcp itself
- tcpcp.c:tcpcp_buffers checks send sequence numbers
- tcpcp.c:tcpcp_fixup adjusts receive buffer to advertized window
- tcpcp.c:tcpcp_fixup sets MSS clamp to value from ICI
- documented request_module race in tcpcp_hooks.c
- README and tcpcp.c: added discussion of usefulness of tcpcp_start
- added description of handover procedure in doc/README.HANDOVER
- minor cleanups here and there
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2002-10-31 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 3:02 TCP connection passing Werner Almesberger
2002-10-31 7:59 ` TCP connection passing, version 1 Werner Almesberger
2002-10-31 23:00 ` Werner Almesberger [this message]
2002-11-01 21:21 ` TCP connection passing, version 3 Werner Almesberger
2002-11-15 4:34 ` TCP connection passing, version 4 Werner Almesberger
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=20021031200017.A21544@almesberger.net \
--to=wa@almesberger.net \
--cc=netdev@oss.sgi.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 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.