mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Angelo Dell'Aera" <buffer@olografix.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: Wed, 23 Feb 2005 12:58:46 +0100	[thread overview]
Message-ID: <20050223125846.674b6175@alnitak.darkstar.net> (raw)
In-Reply-To: <20050222094219.0a8efbe1@dxpl.pdx.osdl.net>

On Tue, 22 Feb 2005 09:42:19 -0800
Stephen Hemminger <shemminger@osdl.org> wrote:


> Probably the best long term solution is to make the protocol choice
> be a property of the destination cache 

[..]
> 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 think it should be nice if we substitute in the struct tcp_opt all the structs
related to the congestion control algorithms with a more generic one which could 
be initialized when the connection is open by reading just one sysctl which defines
the algorithm to be used. This could allow later even a user-space application to
set the congestion control it desires to use.   


> Is there interest in setting up a semi official "-tcp" tree to hold these?
> because it might not be of wide interest or stability to be ready for mainline
> kernel.

I perfectly agree.


--

Angelo Dell'Aera 'buffer' 
Antifork Research, Inc.	  	http://buffer.antifork.org
Metro Olografix


  parent reply	other threads:[~2005-02-23 11:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-22 14:34 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
2005-02-23 11:58   ` Angelo Dell'Aera [this message]
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=20050223125846.674b6175@alnitak.darkstar.net \
    --to=buffer@olografix.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

all inboxes | Powered by JetHome®