mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
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:59:57 +0100	[thread overview]
Message-ID: <20020210205957.A13073@outpost.ds9a.nl> (raw)
In-Reply-To: <20020210164754Z289694-13996+20348@vger.kernel.org>
In-Reply-To: <20020210164754Z289694-13996+20348@vger.kernel.org>; from laudney@21cn.com on Sun, Feb 10, 2002 at 04:49:55PM +0000

On Sun, Feb 10, 2002 at 04:49:55PM +0000, 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??

I've seen people state that T/TCP is fundamentally broken:

http://groups.google.com/groups?q=alan+cox+%22t/tcp%22&hl=en&scoring=d&selm=linux.kernel.E14vGeS-0005Lu-00%40the-village.bc.nu&rnum=2

http://www.xent.com/FoRK-archive/feb99/0255.html

So I'm not sure if it is worth implementing.

Regards,

bert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
Netherlabs BV / Rent-a-Nerd.nl           - Nerd Available -
Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc

  parent reply	other threads:[~2002-02-10 20:00 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
2002-02-10 19:59 ` bert hubert [this message]
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=20020210205957.A13073@outpost.ds9a.nl \
    --to=ahu@ds9a.nl \
    --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®