Subject: Re: [PATCH v2 8/8] Document future removal of sysctl_tcp_* options

From: Eric Dumazet <[email-masked]>
Date: Thu, 22 Oct 2009 06:57:25 +0200

Bill Fink a écrit :

> And as mentioned previously, the global options can be quite useful
> in certain test scenarios.  I also agree the per route settings are
> a very useful addition.  I think the global and per route settings
> are complementary and shouldn't be thought of as in conflict with
> one another.
> 

Absolutely, global setting is a must when an admin wants a quick path.

The more flexible would be to have two bits per route, plus
2 bits on the global configuration.

global conf:
00 : timestamps OFF, unless a route setting is not 00
01 : timestamps ON, unless a route setting is not 00
10 : Force timestamps OFF, ignore route settings (emergency sysadmin request)
11 : Force timestamps ON, ignore route settings 

Route settings (used *only* if global setting is 0Y)
00 : global conf is used
01 : Force timestamps being OFF for this route
10 : Force timestamps being ON for this route
11 : complement global conf