From: Werner Almesberger <wa@almesberger.net>
To: netdev@oss.sgi.com
Subject: TCP connection passing, version 4
Date: Fri, 15 Nov 2002 01:34:52 -0300 [thread overview]
Message-ID: <20021115013452.A11669@almesberger.net> (raw)
In-Reply-To: <20021101182123.A30594@almesberger.net>; from wa@almesberger.net on Fri, Nov 01, 2002 at 06:21:23PM -0300
A minor update:
http://www.almesberger.net/tcpcp/tcpcp-4.tar.gz
The main changes are that TCP_KICK has turned into the slightly
more general TCP_CP_FN option, and that I've written down a few
thoughts on "real" checkpointing in doc/README.CHECKPOINTING
The funny thing is that, when I started writing, I suspected that
checkpointing wouldn't really be possible, but then I realized
how it might actually work (okay, with a few hacks, but ... ;-)
The patch is now relative to 2.5.47.
- Werner
----------------------------------- CHANGES -----------------------------------
Version 4 (15-NOV-2002)
-----------------------
- upgraded to the 2.5.47 kernel
- added doc/README.CHECKPOINTING with a few reflections on how tcpcp could be
abused for "real" checkpointing, where the previous connection owner suddenly
dies
- renamed TCP_KICK to TCP_CP_FN, and added a sub-function code in optval
- renamed tcpcp_kick to tcpcp_activate
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
prev parent reply other threads:[~2002-11-15 4:34 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 ` TCP connection passing, version 2 Werner Almesberger
2002-11-01 21:21 ` TCP connection passing, version 3 Werner Almesberger
2002-11-15 4:34 ` Werner Almesberger [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=20021115013452.A11669@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.