public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baruch Even <baruch@ev-en.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: mlists@danielinux.net, "David S. Miller" <davem@davemloft.net>,
	linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
	Carlo Caini <ccaini@deis.unibo.it>,
	Rosario Firrincieli <rfirrincieli@arces.unibo.it>
Subject: Re: [PATCH] TCP-Hybla proposal
Date: Tue, 22 Feb 2005 20:16:23 +0000	[thread overview]
Message-ID: <421B9317.7000209@ev-en.org> (raw)
In-Reply-To: <20050222094219.0a8efbe1@dxpl.pdx.osdl.net>

Stephen Hemminger wrote:
> On Tue, 22 Feb 2005 15:34:42 +0100
> Daniele Lacamera <mlists@danielinux.net> wrote:
>>One last note: IMHO we really need a better way to select congestion 
>>avoidance scheme between those available, instead of switching each one 
>>on and off. I.e., we can't say how vegas and westwood perform when 
>>switched on together, can we?
> 
> The protocol choices are mutually exclusive, if you walk through the code
> (or do experiments), you find that that only one gets used.  As part of the
> longer term plan, I would like to:
> 	- have one sysctl
> 	- choice by route and destination
> 	- union for fields in control block

I'm currently working on a patch to make it a single sysctl, I've got it 
working (as in, the kernel doesn't crash). I still need to validate the 
actual implementation.

I'd say the next stage is to merge fields as much as possible.

I doubt the real use of selection by route/dest, all of the high-speed 
protocols (except possibly for TCP-Hybla) are intended for sender-only 
servers who push lots of data and should work in all cases and alongside 
  Reno TCP traffic without undue unfairness.

I hope to finish the clean-up and preparation of H-TCP for inclusion in 
the kernel and can then help with the unionisation.

Baruch

  parent reply	other threads:[~2005-02-22 20:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-22 14:34 [PATCH] TCP-Hybla proposal Daniele Lacamera
2005-02-22 15:42 ` Daniele Lacamera
2005-02-22 17:42 ` Stephen Hemminger
2005-02-22 18:03   ` John Heffner
2005-02-22 18:14     ` David S. Miller
2005-02-23  0:41       ` Tobias DiPasquale
2005-02-23  4:22         ` Stephen Hemminger
2005-02-22 19:07   ` David S. Miller
2005-02-22 20:16   ` Baruch Even [this message]
2005-02-23 11:58   ` Angelo Dell'Aera
2005-02-23  4:00 ` Matt Mackall
2005-02-23 17:27   ` Daniele Lacamera

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=421B9317.7000209@ev-en.org \
    --to=baruch@ev-en.org \
    --cc=ccaini@deis.unibo.it \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=mlists@danielinux.net \
    --cc=rfirrincieli@arces.unibo.it \
    --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