netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baruch Even <baruch@ev-en.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: "David S.Miller" <davem@davemloft.net>,
	linux-net@vger.kernel.org, netdev@oss.sgi.com,
	Douglas Leith <doug.leith@nuim.ie>
Subject: Re: [RFC INTRO 0/5] H-TCP congestion control
Date: Fri, 22 Apr 2005 01:48:02 +0100	[thread overview]
Message-ID: <426849C2.7000409@ev-en.org> (raw)
In-Reply-To: <20050311094239.4c59c29d@dxpl.pdx.osdl.net>

Stephen Hemminger wrote:
> On Fri, 11 Mar 2005 18:07:34 +0200 (IST)
> Baruch Even <baruch@ev-en.org> wrote:
> 
> 
>>The following patches are the result of the work of Douglas Leith to implement
>>the H-TCP congestion control proposal. They have since been modified by me
>>(Baruch Even) to port them to kernel 2.6.x, test them and tune them.
>>
>>All patches are against Linux kernel version 2.6.11-bk6. This is currently
>>a preliminary work and is presented for review in order to receive comments to
>>improve this work so it can be accepted to mainline Linux Kernel.
>>
>>The initial development was to add H-TCP to the Linux kernel for testing
>>purposes, it became evident that on 1 Gbit/s links Linux is unable to process
>>the received ack stream fast enough to handle the load. We have patches for
>>that but they proved too hard to be ported to 2.6.11+, we are currently working
>>on them.
>>
>>Baruch
> 
> 
> Are there any IPR encumberance to this like FAST TCP. Earlier versions of
> this patch said:
> 
> 
>>This patch is covered by a pending patent, a license is being worked on to
>>enable the inclusion in Linux. Comments and suggestions on this are also
>>solicited.
> 
> 
> Has this changed?

This has changed now. The code is now released under the GNU GPL v2, 
according to what I was told this effectively implies that any patent 
right that the university will have regarding this technology is 
effectively licensed for use with this code.

Please let me know if there is anything else that we need to do to let 
the review and possible inclusion of our contribution to proceed.

Baruch

  parent reply	other threads:[~2005-04-22  0:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 16:07 [RFC INTRO 0/5] H-TCP congestion control Baruch Even
2005-03-11 16:08 ` [RFC PATCH 1/5] Implement H-TCP congestion control algorithm Baruch Even
2005-03-11 16:09 ` [RFC PATCH 2/5] Adjust alpha according to a function defined in HTCP Baruch Even
2005-03-11 16:10 ` [RFC PATCH 3/5] Adjust alpha to 2*(1-beta) Baruch Even
2005-03-11 16:11 ` [RFC PATCH 4/5] Adjust alpha according to RTT timing Baruch Even
2005-03-11 16:12 ` [RFC PATCH 5/5] Switch in/out of beta=minrtt/maxrtt by bandwidth Baruch Even
2005-03-11 17:42 ` [RFC INTRO 0/5] H-TCP congestion control Stephen Hemminger
2005-03-11 18:38   ` Baruch Even
2005-03-12  4:13     ` David S. Miller
2005-04-22  0:48   ` Baruch Even [this message]
2005-04-22  3:15     ` Jamie Lokier
2005-04-22 11:58       ` Baruch Even

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=426849C2.7000409@ev-en.org \
    --to=baruch@ev-en.org \
    --cc=davem@davemloft.net \
    --cc=doug.leith@nuim.ie \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).