From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Laurence <laudney@21cn.com>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Transaction TCP patch for Linux
Date: Sun, 10 Feb 2002 20:40:35 +0200 [thread overview]
Message-ID: <20020210204035.M20396@mea-ext.zmailer.org> (raw)
In-Reply-To: <20020210164754Z289694-13996+20348@vger.kernel.org>
In-Reply-To: <20020210164754Z289694-13996+20348@vger.kernel.org>; from laudney@21cn.com on Mon, Feb 11, 2002 at 12:50:02AM +0800
On Mon, Feb 11, 2002 at 12:50:02AM +0800, Laurence wrote:
> I'd like to be emailed comments or replies personally.
>
> Transaction TCP is an extension for TCP. Its performance advantage is
> indisputably better than standard TCP. But only FreeBSD integrates
> TTCP into its kernel. So, I've started T/TCP for Linux at
> http://ttcplinux.sourceforge.net or
> http://sourceforge.net/projects/ttcplinux. I'm writing the kernel
> patch for Linux kernel 2.4.2. Is anyone interested in it or have
> anything to say about T/TCP's pros and cons??
http://theory.lcs.mit.edu/~mass/comm.html
http://theory.lcs.mit.edu/~mass/forte96.html
There Mark Smith shows that T/TCP does not (in all error cases)
act the _same_ as TCP, although that does not necessarily mean
it would be wrong.
Reading W.R.Stevens' book "TCP/IP Illustriated, Volume 3"
gives a glimpse of how BSD did things in NET/3 code back
in early 1994-1996, and there I see many odd bits like
per-host route entires containing support data..
> Besides, I've finished some basic codes involving:
> 1. new structures
> 2. newly created or modified funtions mainly related to receiving
>
> If anyone is interested, tell me and I'll send the codes. I don't want
> to upload the codes in CVS at this moment. At least, I want to have a
> basic but compile-able one.
/Matti Aarnio
next prev parent reply other threads:[~2002-02-10 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-10 16:50 Laurence
2002-02-10 18:40 ` Matti Aarnio [this message]
2002-02-10 19:59 ` bert hubert
2002-02-11 1:06 ` Alan Cox
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=20020210204035.M20396@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=laudney@21cn.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®