On 08/28/2015 11:18 PM, David Miller wrote:
...
I don't know about this.
You're adding a new user visible feature bit, but...
The user can set it and silently the kernel will accept it, but this
bit is ignored.
Regardless of it's internal value, we never publish it to the user.
This is just a
From: Florian Westphal
Date: Fri, 28 Aug 2015 14:11:09 +0200
> @@ -418,10 +418,13 @@ enum {
>
> #define RTAX_MAX (__RTAX_MAX - 1)
>
> -#define RTAX_FEATURE_ECN 0x0001
> -#define RTAX_FEATURE_SACK0x0002
> -#define RTAX_FEATURE_TIMESTAMP 0x0004
> -#define RTAX_FEATURE
From: Daniel Borkmann
Currently, the following case doesn't use DCTCP, even if it should:
A responder has f.e. Cubic as system wide default, but for a specific
route to the initiating host, DCTCP is being set in RTAX_CC_ALGO. The
initiating host then uses DCTCP as congestion control, but since th
