public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Tobias DiPasquale <codeslinger@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	John Heffner <jheffner@psc.edu>,
	mlists@danielinux.net, linux-net@vger.kernel.org,
	linux-kernel@vger.kernel.org, ccaini@deis.unibo.it,
	rfirrincieli@arces.unibo.it
Subject: Re: [PATCH] TCP-Hybla proposal
Date: Tue, 22 Feb 2005 20:22:18 -0800	[thread overview]
Message-ID: <421C04FA.8090706@osdl.org> (raw)
In-Reply-To: <876ef97a050222164140968e15@mail.gmail.com>

> On Tue, 22 Feb 2005 10:14:47 -0800, David S. Miller <davem@davemloft.net> wrote:
> 
>>> On Tue, 22 Feb 2005 13:03:11 -0500 (EST)
>>> John Heffner <jheffner@psc.edu> wrote:
>>> 
>>
>>>> > An idea I've been toying with for a while now is completely abstracting
>>>> > congestion control.  Then you could have congestion control loadable
>>>> > modules, which would avoid this mess of experimental algorithms inside the
>>>> > main-line kernel.  If done right, they might be able to work seamlessly
>>>> > with SCTP, too.  The tricky part is making sure the interface is complete
>>>> > enough.
There might be a noticeable performance impact to making it truly 
modular. Calling a function in a module is slower. In some tests, I see 
a 5 to 10% drop in performance when Ethernet driver is a module versus 
builtin.

You might want to look at how the I/O schedulers are configured as an 
example.

>>> 
>>> The symbols exported to allow this would need to be EXPORT_SYMBOL_GPL().
> 
> 
> Why's that?

Because the kernel developers who hold the collective copyright on the 
existing GPL TCP code do not want some vendor producing a closed source 
binary module of "enhanced TCP".

  reply	other threads:[~2005-02-23  4:22 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 [this message]
2005-02-22 19:07   ` David S. Miller
2005-02-22 20:16   ` Baruch Even
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=421C04FA.8090706@osdl.org \
    --to=shemminger@osdl.org \
    --cc=ccaini@deis.unibo.it \
    --cc=codeslinger@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jheffner@psc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=mlists@danielinux.net \
    --cc=rfirrincieli@arces.unibo.it \
    /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