From: Patrick McHardy <kaber@trash.net>
To: Glen Turner <glen.turner@aarnet.edu.au>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH] Add TCPCONG target to patch-o-matic
Date: Mon, 09 Oct 2006 17:12:10 +0200 [thread overview]
Message-ID: <452A66CA.70603@trash.net> (raw)
In-Reply-To: <4524BBB2.2000109@aarnet.edu.au>
Glen Turner wrote:
>
> Hi folks,
>
> I have created a kernel module and iptables shared library
> to allow netfilter to set the TCP congestion control
> algorithm.
>
> This has three major uses: selecting differing algorithms
> for wired and non-wired interfaces; selecting differing
> algorithms for close and far hosts; and selecting differing
> algorithms for comparison testing.
>
> Thanks to the hint from Pablo Neira Ayuso I have put this
> into the patch-o-matic format. This has been tested against
> iptables-1.3.6 and linux-2.6.18.
>
> A SVN diff against patch-o-matic follows, which I'm hoping
> Thunderbird doesn't mangle. Since I'm not familiar with SVN
> please let me know if this isn't the desired patch format.
>
> I would hope that this facility can become a standard part of
> the kernel and iptables. Please let me know what I need to
> do to follow that path.
I don't think iptables is the right place to do this. It should
be controllable through routing IMO (which can already control
some aspects of congestion control).
next prev parent reply other threads:[~2006-10-09 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 7:12 Patch-o-matic says "unable to find ladd slot" in Makefile Glen Turner
2006-10-04 19:54 ` Pablo Neira Ayuso
2006-10-05 8:00 ` [PATCH] Add TCPCONG target to patch-o-matic Glen Turner
2006-10-09 15:12 ` Patrick McHardy [this message]
2006-10-10 7:00 ` Glen Turner
2006-10-11 5:32 ` Patrick McHardy
2006-10-11 20:04 ` Stephen Hemminger
2006-10-12 0:37 ` Glen Turner
2006-10-12 0:57 ` Patrick McHardy
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=452A66CA.70603@trash.net \
--to=kaber@trash.net \
--cc=glen.turner@aarnet.edu.au \
--cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.