forked from ~ljy/RK356X_SDK_RELEASE
kernel/net/netfilter/ipvs/Kconfig
.. .. @@ -1,3 +1,4 @@ 1 1 2 # 2 3 # IP Virtual Server configuration 3 4 # .. .. @@ -5,7 +6,7 @@ 5 6 tristate "IP virtual server support" 6 7 depends on NET && INET && NETFILTER 7 8 depends on (NF_CONNTRACK || NF_CONNTRACK=n) 8 9 9 10 IP Virtual Server support will let you build a high-performance 10 11 virtual server based on cluster of two or more real servers. This 11 12 option must be enabled for at least one of the clustered computers .. .. @@ -28,16 +29,15 @@ 28 29 config IP_VS_IPV6 29 30 bool "IPv6 support for IPVS" 30 31 depends on IPV6 = y || IP_VS = IPV6 31 32 32 select NF_DEFRAG_IPV6 33 33 34 34 Add IPv6 support to IPVS. 35 35 36 36 Say Y if unsure. 37 37 38 38 config IP_VS_DEBUG 39 39 bool "IP virtual server debugging" 40 40 41 41 Say Y here if you want to get additional messages useful in 42 42 debugging the IP virtual server code. You can change the debug 43 43 level in /proc/sys/net/ipv4/vs/debug_level .. .. @@ -46,7 +46,7 @@ 46 46 int "IPVS connection table size (the Nth power of 2)" 47 47 range 8 20 48 48 default 12 49 49 50 50 The IPVS connection hash table uses the chaining scheme to handle 51 51 hash collisions. Using a big IPVS connection hash table will greatly 52 52 reduce conflicts when there are hundreds of thousands of connections .. .. @@ -77,13 +77,13 @@ 77 77 78 78 config IP_VS_PROTO_TCP 79 79 bool "TCP load balancing support" 80 80 81 81 This option enables support for load balancing TCP transport 82 82 protocol. Say Y if unsure. 83 83 84 84 config IP_VS_PROTO_UDP 85 85 bool "UDP load balancing support" 86 86 87 87 This option enables support for load balancing UDP transport 88 88 protocol. Say Y if unsure. 89 89 .. .. @@ -92,20 +92,20 @@ 92 92 93 93 config IP_VS_PROTO_ESP 94 94 bool "ESP load balancing support" 95 95 96 96 This option enables support for load balancing ESP (Encapsulation 97 97 Security Payload) transport protocol. Say Y if unsure. 98 98 99 99 config IP_VS_PROTO_AH 100 100 bool "AH load balancing support" 101 101 102 102 This option enables support for load balancing AH (Authentication 103 103 Header) transport protocol. Say Y if unsure. 104 104 105 105 config IP_VS_PROTO_SCTP 106 106 bool "SCTP load balancing support" 107 107 select LIBCRC32C 108 108 109 109 This option enables support for load balancing SCTP transport 110 110 protocol. Say Y if unsure. 111 111 .. .. @@ -113,7 +113,7 @@ 113 113 114 114 config IP_VS_RR 115 115 tristate "round-robin scheduling" 116 116 117 117 The robin-robin scheduling algorithm simply directs network 118 118 connections to different real servers in a round-robin manner. 119 119 .. .. @@ -122,7 +122,7 @@ 122 122 123 123 config IP_VS_WRR 124 124 tristate "weighted round-robin scheduling" 125 125 126 126 The weighted robin-robin scheduling algorithm directs network 127 127 connections to different real servers based on server weights 128 128 in a round-robin manner. Servers with higher weights receive .. .. @@ -134,8 +134,8 @@ 134 134 module, choose M here. If unsure, say N. 135 135 136 136 config IP_VS_LC 137 138 137 138 139 139 The least-connection scheduling algorithm directs network 140 140 connections to the server with the least number of active 141 141 connections. .. .. @@ -144,8 +144,8 @@ 144 144 module, choose M here. If unsure, say N. 145 145 146 146 config IP_VS_WLC 147 148 147 148 149 149 The weighted least-connection scheduling algorithm directs network 150 150 connections to the server with the least active connections 151 151 normalized by the server weight. .. .. @@ -155,7 +155,7 @@ 155 155 156 156 config IP_VS_FO 157 157 tristate "weighted failover scheduling" 158 158 159 159 The weighted failover scheduling algorithm directs network 160 160 connections to the server with the highest weight that is 161 161 currently available. .. .. @@ -165,7 +165,7 @@ 165 165 166 166 config IP_VS_OVF 167 167 tristate "weighted overflow scheduling" 168 168 169 169 The weighted overflow scheduling algorithm directs network 170 170 connections to the server with the highest weight that is 171 171 currently available and overflows to the next when active .. .. @@ -176,7 +176,7 @@ 176 176 177 177 config IP_VS_LBLC 178 178 tristate "locality-based least-connection scheduling" 179 179 180 180 The locality-based least-connection scheduling algorithm is for 181 181 destination IP load balancing. It is usually used in cache cluster. 182 182 This algorithm usually directs packet destined for an IP address to .. .. @@ -190,7 +190,7 @@ 190 190 191 191 config IP_VS_LBLCR 192 192 tristate "locality-based least-connection with replication scheduling" 193 193 194 194 The locality-based least-connection with replication scheduling 195 195 algorithm is also for destination IP load balancing. It is 196 196 usually used in cache cluster. It differs from the LBLC scheduling .. .. @@ -208,7 +208,7 @@ 208 208 209 209 config IP_VS_DH 210 210 tristate "destination hashing scheduling" 211 211 212 212 The destination hashing scheduling algorithm assigns network 213 213 connections to the servers through looking up a statically assigned 214 214 hash table by their destination IP addresses. .. .. @@ -218,7 +218,7 @@ 218 218 219 219 config IP_VS_SH 220 220 tristate "source hashing scheduling" 221 221 222 222 The source hashing scheduling algorithm assigns network 223 223 connections to the servers through looking up a statically assigned 224 224 hash table by their source IP addresses. .. .. @@ -228,7 +228,7 @@ 228 228 229 229 config IP_VS_MH 230 230 tristate "maglev hashing scheduling" 231 231 232 232 The maglev consistent hashing scheduling algorithm provides the 233 233 Google's Maglev hashing algorithm as a IPVS scheduler. It assigns 234 234 network connections to the servers through looking up a statically .. .. @@ -247,7 +247,7 @@ 247 247 248 248 config IP_VS_SED 249 249 tristate "shortest expected delay scheduling" 250 250 251 251 The shortest expected delay scheduling algorithm assigns network 252 252 connections to the server with the shortest expected delay. The 253 253 expected delay that the job will experience is (Ci + 1) / Ui if .. .. @@ -260,7 +260,7 @@ 260 260 261 261 config IP_VS_NQ 262 262 tristate "never queue scheduling" 263 263 264 264 The never queue scheduling algorithm adopts a two-speed model. 265 265 When there is an idle server available, the job will be sent to 266 266 the idle server, instead of waiting for a fast one. When there .. .. @@ -277,7 +277,7 @@ 277 277 int "IPVS source hashing table size (the Nth power of 2)" 278 278 range 4 20 279 279 default 8 280 280 281 281 The source hashing scheduler maps source IPs to destinations 282 282 stored in a hash table. This table is tiled by each destination 283 283 until all slots in the table are filled. When using weights to .. .. @@ -292,7 +292,7 @@ 292 292 int "IPVS maglev hashing table index of size (the prime numbers)" 293 293 range 8 17 294 294 default 12 295 295 296 296 The maglev hashing scheduler maps source IPs to destinations 297 297 stored in a hash table. This table is assigned by a preference 298 298 list of the positions to each destination until all slots in .. .. @@ -311,7 +311,7 @@ 311 311 depends on IP_VS_PROTO_TCP && NF_CONNTRACK && NF_NAT && \ 312 312 NF_CONNTRACK_FTP 313 313 select IP_VS_NFCT 314 314 315 315 FTP is a protocol that transfers IP address and/or port number in 316 316 the payload. In the virtual server via Network Address Translation, 317 317 the IP address and port number of real servers cannot be sent to .. .. @@ -325,16 +325,16 @@ 325 325 config IP_VS_NFCT 326 326 bool "Netfilter connection tracking" 327 327 depends on NF_CONNTRACK 328 328 329 329 The Netfilter connection tracking support allows the IPVS 330 330 connection state to be exported to the Netfilter framework 331 331 for filtering purposes. 332 332 333 333 config IP_VS_PE_SIP 334 334 tristate "SIP persistence engine" 335 335 336 336 depends on NF_CONNTRACK_SIP 337 337 338 338 Allow persistence based on the SIP Call-ID 339 339 340 340 endif # IP_VS
