From: Daniel Borkmann <dborkman@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: hannes@stressinduktion.org, fw@strlen.de, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/4] net: allow setting congctl via routing table
Date: Tue, 09 Dec 2014 22:22:02 +0100 [thread overview]
Message-ID: <548767FA.2020402@redhat.com> (raw)
In-Reply-To: <20141209.155844.1175199719902606020.davem@davemloft.net>
On 12/09/2014 09:58 PM, David Miller wrote:
> From: Daniel Borkmann <dborkman@redhat.com>
> Date: Sun, 7 Dec 2014 00:39:19 +0100
>
>> This is the second part of our work and allows for setting the congestion
>> control algorithm via routing table. For details, please see individual
>> patches.
>>
>> Joint work with Florian Westphal, suggested by Hannes Frederic Sowa.
>>
>> Patch for iproute2: http://patchwork.ozlabs.org/patch/418149/
>>
>> Thanks!
>>
>> v1->v2:
>> - Very sorry, I noticed I had decnet disabled during testing.
>> Added missing header include in decnet, rest as is.
>
> I don't like how you have to explicitly load the congestion control
> module before asking for it to be used in the route entry metric.
>
> It should request the module automatically just like the stack already
> does for other cases.
Ok, sure, adding auto-loading should not be a problem. Will respin
with that tomorrow.
Thanks.
prev parent reply other threads:[~2014-12-09 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 23:39 [PATCH net-next v2 0/4] net: allow setting congctl via routing table Daniel Borkmann
2014-12-06 23:39 ` [PATCH net-next v2 1/4] net: tcp: refactor reinitialization of congestion control Daniel Borkmann
2014-12-06 23:39 ` [PATCH net-next v2 2/4] net: tcp: add key management to " Daniel Borkmann
2014-12-06 23:39 ` [PATCH net-next v2 3/4] net: tcp: add RTAX_CC_ALGO fib handling Daniel Borkmann
2014-12-06 23:39 ` [PATCH net-next v2 4/4] net: tcp: add per route congestion control Daniel Borkmann
2014-12-09 20:58 ` [PATCH net-next v2 0/4] net: allow setting congctl via routing table David Miller
2014-12-09 21:22 ` Daniel Borkmann [this message]
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=548767FA.2020402@redhat.com \
--to=dborkman@redhat.com \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.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).