1 # SPDX-License-Identifier: GPL-2.0-only <<
2 # 1 #
3 # Traffic control configuration. 2 # Traffic control configuration.
4 # 3 #
5 4
6 menuconfig NET_SCHED 5 menuconfig NET_SCHED
7 bool "QoS and/or fair queueing" 6 bool "QoS and/or fair queueing"
8 select NET_SCH_FIFO 7 select NET_SCH_FIFO
9 help !! 8 ---help---
10 When the kernel has several packets 9 When the kernel has several packets to send out over a network
11 device, it has to decide which ones 10 device, it has to decide which ones to send first, which ones to
12 delay, and which ones to drop. This 11 delay, and which ones to drop. This is the job of the queueing
13 disciplines, several different algor 12 disciplines, several different algorithms for how to do this
14 "fairly" have been proposed. 13 "fairly" have been proposed.
15 14
16 If you say N here, you will get the 15 If you say N here, you will get the standard packet scheduler, which
17 is a FIFO (first come, first served) 16 is a FIFO (first come, first served). If you say Y here, you will be
18 able to choose from among several al 17 able to choose from among several alternative algorithms which can
19 then be attached to different networ 18 then be attached to different network devices. This is useful for
20 example if some of your network devi 19 example if some of your network devices are real time devices that
21 need a certain minimum data flow rat 20 need a certain minimum data flow rate, or if you need to limit the
22 maximum data flow rate for traffic w 21 maximum data flow rate for traffic which matches specified criteria.
23 This code is considered to be experi 22 This code is considered to be experimental.
24 23
25 To administer these schedulers, you' 24 To administer these schedulers, you'll need the user-level utilities
26 from the package iproute2+tc at 25 from the package iproute2+tc at
27 <https://www.kernel.org/pub/linux/ut 26 <https://www.kernel.org/pub/linux/utils/net/iproute2/>. That package
28 also contains some documentation; fo 27 also contains some documentation; for more, check out
29 <http://www.linuxfoundation.org/coll 28 <http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2>.
30 29
31 This Quality of Service (QoS) suppor 30 This Quality of Service (QoS) support will enable you to use
32 Differentiated Services (diffserv) a 31 Differentiated Services (diffserv) and Resource Reservation Protocol
33 (RSVP) on your Linux router if you a 32 (RSVP) on your Linux router if you also say Y to the corresponding
34 classifiers below. Documentation an 33 classifiers below. Documentation and software is at
35 <http://diffserv.sourceforge.net/>. 34 <http://diffserv.sourceforge.net/>.
36 35
37 If you say Y here and to "/proc file 36 If you say Y here and to "/proc file system" below, you will be able
38 to read status information about pac 37 to read status information about packet schedulers from the file
39 /proc/net/psched. 38 /proc/net/psched.
40 39
41 The available schedulers are listed 40 The available schedulers are listed in the following questions; you
42 can say Y to as many as you like. If 41 can say Y to as many as you like. If unsure, say N now.
43 42
44 if NET_SCHED 43 if NET_SCHED
45 44
46 comment "Queueing/Scheduling" 45 comment "Queueing/Scheduling"
47 46
48 config NET_SCH_HTB 47 config NET_SCH_HTB
49 tristate "Hierarchical Token Bucket (H 48 tristate "Hierarchical Token Bucket (HTB)"
50 help !! 49 ---help---
51 Say Y here if you want to use the Hi 50 Say Y here if you want to use the Hierarchical Token Buckets (HTB)
52 packet scheduling algorithm. See 51 packet scheduling algorithm. See
53 <http://luxik.cdi.cz/~devik/qos/htb/ 52 <http://luxik.cdi.cz/~devik/qos/htb/> for complete manual and
54 in-depth articles. 53 in-depth articles.
55 54
56 HTB is very similar to CBQ regarding 55 HTB is very similar to CBQ regarding its goals however is has
57 different properties and different a 56 different properties and different algorithm.
58 57
59 To compile this code as a module, ch 58 To compile this code as a module, choose M here: the
60 module will be called sch_htb. 59 module will be called sch_htb.
61 60
62 config NET_SCH_HFSC 61 config NET_SCH_HFSC
63 tristate "Hierarchical Fair Service Cu 62 tristate "Hierarchical Fair Service Curve (HFSC)"
64 help !! 63 ---help---
65 Say Y here if you want to use the Hi 64 Say Y here if you want to use the Hierarchical Fair Service Curve
66 (HFSC) packet scheduling algorithm. 65 (HFSC) packet scheduling algorithm.
67 66
68 To compile this code as a module, ch 67 To compile this code as a module, choose M here: the
69 module will be called sch_hfsc. 68 module will be called sch_hfsc.
70 69
71 config NET_SCH_PRIO 70 config NET_SCH_PRIO
72 tristate "Multi Band Priority Queueing 71 tristate "Multi Band Priority Queueing (PRIO)"
73 help !! 72 ---help---
74 Say Y here if you want to use an n-b 73 Say Y here if you want to use an n-band priority queue packet
75 scheduler. 74 scheduler.
76 75
77 To compile this code as a module, ch 76 To compile this code as a module, choose M here: the
78 module will be called sch_prio. 77 module will be called sch_prio.
79 78
80 config NET_SCH_MULTIQ 79 config NET_SCH_MULTIQ
81 tristate "Hardware Multiqueue-aware Mu 80 tristate "Hardware Multiqueue-aware Multi Band Queuing (MULTIQ)"
82 help !! 81 ---help---
83 Say Y here if you want to use an n-b 82 Say Y here if you want to use an n-band queue packet scheduler
84 to support devices that have multipl 83 to support devices that have multiple hardware transmit queues.
85 84
86 To compile this code as a module, ch 85 To compile this code as a module, choose M here: the
87 module will be called sch_multiq. 86 module will be called sch_multiq.
88 87
89 config NET_SCH_RED 88 config NET_SCH_RED
90 tristate "Random Early Detection (RED) 89 tristate "Random Early Detection (RED)"
91 help !! 90 ---help---
92 Say Y here if you want to use the Ra 91 Say Y here if you want to use the Random Early Detection (RED)
93 packet scheduling algorithm. 92 packet scheduling algorithm.
94 93
95 See the top of <file:net/sched/sch_r 94 See the top of <file:net/sched/sch_red.c> for more details.
96 95
97 To compile this code as a module, ch 96 To compile this code as a module, choose M here: the
98 module will be called sch_red. 97 module will be called sch_red.
99 98
100 config NET_SCH_SFB 99 config NET_SCH_SFB
101 tristate "Stochastic Fair Blue (SFB)" 100 tristate "Stochastic Fair Blue (SFB)"
102 help !! 101 ---help---
103 Say Y here if you want to use the St 102 Say Y here if you want to use the Stochastic Fair Blue (SFB)
104 packet scheduling algorithm. 103 packet scheduling algorithm.
105 104
106 See the top of <file:net/sched/sch_s 105 See the top of <file:net/sched/sch_sfb.c> for more details.
107 106
108 To compile this code as a module, ch 107 To compile this code as a module, choose M here: the
109 module will be called sch_sfb. 108 module will be called sch_sfb.
110 109
111 config NET_SCH_SFQ 110 config NET_SCH_SFQ
112 tristate "Stochastic Fairness Queueing 111 tristate "Stochastic Fairness Queueing (SFQ)"
113 help !! 112 ---help---
114 Say Y here if you want to use the St 113 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
115 packet scheduling algorithm. 114 packet scheduling algorithm.
116 115
117 See the top of <file:net/sched/sch_s 116 See the top of <file:net/sched/sch_sfq.c> for more details.
118 117
119 To compile this code as a module, ch 118 To compile this code as a module, choose M here: the
120 module will be called sch_sfq. 119 module will be called sch_sfq.
121 120
122 config NET_SCH_TEQL 121 config NET_SCH_TEQL
123 tristate "True Link Equalizer (TEQL)" 122 tristate "True Link Equalizer (TEQL)"
124 help !! 123 ---help---
125 Say Y here if you want to use the Tr 124 Say Y here if you want to use the True Link Equalizer (TLE) packet
126 scheduling algorithm. This queueing 125 scheduling algorithm. This queueing discipline allows the combination
127 of several physical devices into one 126 of several physical devices into one virtual device.
128 127
129 See the top of <file:net/sched/sch_t 128 See the top of <file:net/sched/sch_teql.c> for more details.
130 129
131 To compile this code as a module, ch 130 To compile this code as a module, choose M here: the
132 module will be called sch_teql. 131 module will be called sch_teql.
133 132
134 config NET_SCH_TBF 133 config NET_SCH_TBF
135 tristate "Token Bucket Filter (TBF)" 134 tristate "Token Bucket Filter (TBF)"
136 help !! 135 ---help---
137 Say Y here if you want to use the To 136 Say Y here if you want to use the Token Bucket Filter (TBF) packet
138 scheduling algorithm. 137 scheduling algorithm.
139 138
140 See the top of <file:net/sched/sch_t 139 See the top of <file:net/sched/sch_tbf.c> for more details.
141 140
142 To compile this code as a module, ch 141 To compile this code as a module, choose M here: the
143 module will be called sch_tbf. 142 module will be called sch_tbf.
144 143
145 config NET_SCH_CBS 144 config NET_SCH_CBS
146 tristate "Credit Based Shaper (CBS)" 145 tristate "Credit Based Shaper (CBS)"
147 help !! 146 ---help---
148 Say Y here if you want to use the Cr 147 Say Y here if you want to use the Credit Based Shaper (CBS) packet
149 scheduling algorithm. 148 scheduling algorithm.
150 149
151 See the top of <file:net/sched/sch_c 150 See the top of <file:net/sched/sch_cbs.c> for more details.
152 151
153 To compile this code as a module, ch 152 To compile this code as a module, choose M here: the
154 module will be called sch_cbs. 153 module will be called sch_cbs.
155 154
156 config NET_SCH_ETF 155 config NET_SCH_ETF
157 tristate "Earliest TxTime First (ETF)" 156 tristate "Earliest TxTime First (ETF)"
158 help 157 help
159 Say Y here if you want to use the Ea 158 Say Y here if you want to use the Earliest TxTime First (ETF) packet
160 scheduling algorithm. 159 scheduling algorithm.
161 160
162 See the top of <file:net/sched/sch_e 161 See the top of <file:net/sched/sch_etf.c> for more details.
163 162
164 To compile this code as a module, ch 163 To compile this code as a module, choose M here: the
165 module will be called sch_etf. 164 module will be called sch_etf.
166 165
167 config NET_SCH_MQPRIO_LIB <<
168 tristate <<
169 help <<
170 Common library for manipulating mqpr <<
171 <<
172 config NET_SCH_TAPRIO <<
173 tristate "Time Aware Priority (taprio) <<
174 select NET_SCH_MQPRIO_LIB <<
175 help <<
176 Say Y here if you want to use the Ti <<
177 scheduling algorithm. <<
178 <<
179 See the top of <file:net/sched/sch_t <<
180 <<
181 To compile this code as a module, ch <<
182 module will be called sch_taprio. <<
183 <<
184 config NET_SCH_GRED 166 config NET_SCH_GRED
185 tristate "Generic Random Early Detecti 167 tristate "Generic Random Early Detection (GRED)"
186 help !! 168 ---help---
187 Say Y here if you want to use the Ge 169 Say Y here if you want to use the Generic Random Early Detection
188 (GRED) packet scheduling algorithm f 170 (GRED) packet scheduling algorithm for some of your network devices
189 (see the top of <file:net/sched/sch_ 171 (see the top of <file:net/sched/sch_red.c> for details and
190 references about the algorithm). 172 references about the algorithm).
191 173
192 To compile this code as a module, ch 174 To compile this code as a module, choose M here: the
193 module will be called sch_gred. 175 module will be called sch_gred.
194 176
195 config NET_SCH_NETEM 177 config NET_SCH_NETEM
196 tristate "Network emulator (NETEM)" 178 tristate "Network emulator (NETEM)"
197 help !! 179 ---help---
198 Say Y if you want to emulate network 180 Say Y if you want to emulate network delay, loss, and packet
199 re-ordering. This is often useful to 181 re-ordering. This is often useful to simulate networks when
200 testing applications or protocols. 182 testing applications or protocols.
201 183
202 To compile this driver as a module, 184 To compile this driver as a module, choose M here: the module
203 will be called sch_netem. 185 will be called sch_netem.
204 186
205 If unsure, say N. 187 If unsure, say N.
206 188
207 config NET_SCH_DRR 189 config NET_SCH_DRR
208 tristate "Deficit Round Robin schedule 190 tristate "Deficit Round Robin scheduler (DRR)"
209 help 191 help
210 Say Y here if you want to use the De 192 Say Y here if you want to use the Deficit Round Robin (DRR) packet
211 scheduling algorithm. 193 scheduling algorithm.
212 194
213 To compile this driver as a module, 195 To compile this driver as a module, choose M here: the module
214 will be called sch_drr. 196 will be called sch_drr.
215 197
216 If unsure, say N. 198 If unsure, say N.
217 199
218 config NET_SCH_MQPRIO 200 config NET_SCH_MQPRIO
219 tristate "Multi-queue priority schedul 201 tristate "Multi-queue priority scheduler (MQPRIO)"
220 select NET_SCH_MQPRIO_LIB <<
221 help 202 help
222 Say Y here if you want to use the Mu 203 Say Y here if you want to use the Multi-queue Priority scheduler.
223 This scheduler allows QOS to be offl 204 This scheduler allows QOS to be offloaded on NICs that have support
224 for offloading QOS schedulers. 205 for offloading QOS schedulers.
225 206
226 To compile this driver as a module, 207 To compile this driver as a module, choose M here: the module will
227 be called sch_mqprio. 208 be called sch_mqprio.
228 209
229 If unsure, say N. 210 If unsure, say N.
230 211
231 config NET_SCH_SKBPRIO 212 config NET_SCH_SKBPRIO
232 tristate "SKB priority queue scheduler 213 tristate "SKB priority queue scheduler (SKBPRIO)"
233 help 214 help
234 Say Y here if you want to use the SK 215 Say Y here if you want to use the SKB priority queue
235 scheduler. This schedules packets ac 216 scheduler. This schedules packets according to skb->priority,
236 which is useful for request packets 217 which is useful for request packets in DoS mitigation systems such
237 as Gatekeeper. 218 as Gatekeeper.
238 219
239 To compile this driver as a module, 220 To compile this driver as a module, choose M here: the module will
240 be called sch_skbprio. 221 be called sch_skbprio.
241 222
242 If unsure, say N. 223 If unsure, say N.
243 224
244 config NET_SCH_CHOKE 225 config NET_SCH_CHOKE
245 tristate "CHOose and Keep responsive f 226 tristate "CHOose and Keep responsive flow scheduler (CHOKE)"
246 help 227 help
247 Say Y here if you want to use the CH 228 Say Y here if you want to use the CHOKe packet scheduler (CHOose
248 and Keep for responsive flows, CHOos 229 and Keep for responsive flows, CHOose and Kill for unresponsive
249 flows). This is a variation of RED w !! 230 flows). This is a variation of RED which trys to penalize flows
250 that monopolize the queue. 231 that monopolize the queue.
251 232
252 To compile this code as a module, ch 233 To compile this code as a module, choose M here: the
253 module will be called sch_choke. 234 module will be called sch_choke.
254 235
255 config NET_SCH_QFQ 236 config NET_SCH_QFQ
256 tristate "Quick Fair Queueing schedule 237 tristate "Quick Fair Queueing scheduler (QFQ)"
257 help 238 help
258 Say Y here if you want to use the Qu 239 Say Y here if you want to use the Quick Fair Queueing Scheduler (QFQ)
259 packet scheduling algorithm. 240 packet scheduling algorithm.
260 241
261 To compile this driver as a module, 242 To compile this driver as a module, choose M here: the module
262 will be called sch_qfq. 243 will be called sch_qfq.
263 244
264 If unsure, say N. 245 If unsure, say N.
265 246
266 config NET_SCH_CODEL 247 config NET_SCH_CODEL
267 tristate "Controlled Delay AQM (CODEL) 248 tristate "Controlled Delay AQM (CODEL)"
268 help 249 help
269 Say Y here if you want to use the Co 250 Say Y here if you want to use the Controlled Delay (CODEL)
270 packet scheduling algorithm. 251 packet scheduling algorithm.
271 252
272 To compile this driver as a module, 253 To compile this driver as a module, choose M here: the module
273 will be called sch_codel. 254 will be called sch_codel.
274 255
275 If unsure, say N. 256 If unsure, say N.
276 257
277 config NET_SCH_FQ_CODEL 258 config NET_SCH_FQ_CODEL
278 tristate "Fair Queue Controlled Delay 259 tristate "Fair Queue Controlled Delay AQM (FQ_CODEL)"
279 help 260 help
280 Say Y here if you want to use the FQ 261 Say Y here if you want to use the FQ Controlled Delay (FQ_CODEL)
281 packet scheduling algorithm. 262 packet scheduling algorithm.
282 263
283 To compile this driver as a module, 264 To compile this driver as a module, choose M here: the module
284 will be called sch_fq_codel. 265 will be called sch_fq_codel.
285 266
286 If unsure, say N. 267 If unsure, say N.
287 268
288 config NET_SCH_CAKE 269 config NET_SCH_CAKE
289 tristate "Common Applications Kept Enh 270 tristate "Common Applications Kept Enhanced (CAKE)"
290 help 271 help
291 Say Y here if you want to use the Co 272 Say Y here if you want to use the Common Applications Kept Enhanced
292 (CAKE) queue management algorithm. !! 273 (CAKE) queue management algorithm.
293 274
294 To compile this driver as a module, 275 To compile this driver as a module, choose M here: the module
295 will be called sch_cake. 276 will be called sch_cake.
296 277
297 If unsure, say N. 278 If unsure, say N.
298 279
299 config NET_SCH_FQ 280 config NET_SCH_FQ
300 tristate "Fair Queue" 281 tristate "Fair Queue"
301 help 282 help
302 Say Y here if you want to use the FQ 283 Say Y here if you want to use the FQ packet scheduling algorithm.
303 284
304 FQ does flow separation, and is able 285 FQ does flow separation, and is able to respect pacing requirements
305 set by TCP stack into sk->sk_pacing_ !! 286 set by TCP stack into sk->sk_pacing_rate (for localy generated
306 traffic) 287 traffic)
307 288
308 To compile this driver as a module, 289 To compile this driver as a module, choose M here: the module
309 will be called sch_fq. 290 will be called sch_fq.
310 291
311 If unsure, say N. 292 If unsure, say N.
312 293
313 config NET_SCH_HHF 294 config NET_SCH_HHF
314 tristate "Heavy-Hitter Filter (HHF)" 295 tristate "Heavy-Hitter Filter (HHF)"
315 help 296 help
316 Say Y here if you want to use the He 297 Say Y here if you want to use the Heavy-Hitter Filter (HHF)
317 packet scheduling algorithm. 298 packet scheduling algorithm.
318 299
319 To compile this driver as a module, 300 To compile this driver as a module, choose M here: the module
320 will be called sch_hhf. 301 will be called sch_hhf.
321 302
322 config NET_SCH_PIE 303 config NET_SCH_PIE
323 tristate "Proportional Integral contro 304 tristate "Proportional Integral controller Enhanced (PIE) scheduler"
324 help 305 help
325 Say Y here if you want to use the Pr 306 Say Y here if you want to use the Proportional Integral controller
326 Enhanced scheduler packet scheduling 307 Enhanced scheduler packet scheduling algorithm.
327 For more information, please see htt !! 308 For more information, please see
>> 309 http://tools.ietf.org/html/draft-pan-tsvwg-pie-00
328 310
329 To compile this driver as a module, 311 To compile this driver as a module, choose M here: the module
330 will be called sch_pie. 312 will be called sch_pie.
331 313
332 If unsure, say N. 314 If unsure, say N.
333 315
334 config NET_SCH_FQ_PIE <<
335 depends on NET_SCH_PIE <<
336 tristate "Flow Queue Proportional Inte <<
337 help <<
338 Say Y here if you want to use the Fl <<
339 controller Enhanced (FQ-PIE) packet <<
340 For more information, please see htt <<
341 <<
342 To compile this driver as a module, <<
343 will be called sch_fq_pie. <<
344 <<
345 If unsure, say N. <<
346 <<
347 config NET_SCH_INGRESS 316 config NET_SCH_INGRESS
348 tristate "Ingress/classifier-action Qd 317 tristate "Ingress/classifier-action Qdisc"
349 depends on NET_CLS_ACT 318 depends on NET_CLS_ACT
350 select NET_XGRESS !! 319 select NET_INGRESS
351 help !! 320 select NET_EGRESS
>> 321 ---help---
352 Say Y here if you want to use classi 322 Say Y here if you want to use classifiers for incoming and/or outgoing
353 packets. This qdisc doesn't do anyth 323 packets. This qdisc doesn't do anything else besides running classifiers,
354 which can also have actions attached 324 which can also have actions attached to them. In case of outgoing packets,
355 classifiers that this qdisc holds ar 325 classifiers that this qdisc holds are executed in the transmit path
356 before real enqueuing to an egress q 326 before real enqueuing to an egress qdisc happens.
357 327
358 If unsure, say Y. 328 If unsure, say Y.
359 329
360 To compile this code as a module, ch 330 To compile this code as a module, choose M here: the module will be
361 called sch_ingress with alias of sch 331 called sch_ingress with alias of sch_clsact.
362 332
363 config NET_SCH_PLUG 333 config NET_SCH_PLUG
364 tristate "Plug network traffic until r 334 tristate "Plug network traffic until release (PLUG)"
365 help !! 335 ---help---
366 336
367 This queuing discipline allows users 337 This queuing discipline allows userspace to plug/unplug a network
368 output queue, using the netlink inte 338 output queue, using the netlink interface. When it receives an
369 enqueue command it inserts a plug in 339 enqueue command it inserts a plug into the outbound queue that
370 causes following packets to enqueue 340 causes following packets to enqueue until a dequeue command arrives
371 over netlink, causing the plug to be 341 over netlink, causing the plug to be removed and resuming the normal
372 packet flow. 342 packet flow.
373 343
374 This module also provides a generic 344 This module also provides a generic "network output buffering"
375 functionality (aka output commit), w 345 functionality (aka output commit), wherein upon arrival of a dequeue
376 command, only packets up to the firs 346 command, only packets up to the first plug are released for delivery.
377 The Remus HA project uses this modul 347 The Remus HA project uses this module to enable speculative execution
378 of virtual machines by allowing the 348 of virtual machines by allowing the generated network output to be rolled
379 back if needed. 349 back if needed.
380 350
381 For more information, please refer t 351 For more information, please refer to <http://wiki.xenproject.org/wiki/Remus>
382 352
383 Say Y here if you are using this ker 353 Say Y here if you are using this kernel for Xen dom0 and
384 want to protect Xen guests with Remu 354 want to protect Xen guests with Remus.
385 355
386 To compile this code as a module, ch 356 To compile this code as a module, choose M here: the
387 module will be called sch_plug. 357 module will be called sch_plug.
388 358
389 config NET_SCH_ETS <<
390 tristate "Enhanced transmission select <<
391 help <<
392 The Enhanced Transmission Selection <<
393 queuing discipline that merges funct <<
394 qdiscs in one scheduler. ETS makes i <<
395 strict and bandwidth-sharing bands t <<
396 selection described in 802.1Qaz. <<
397 <<
398 Say Y here if you want to use the ET <<
399 algorithm. <<
400 <<
401 To compile this driver as a module, <<
402 will be called sch_ets. <<
403 <<
404 If unsure, say N. <<
405 <<
406 menuconfig NET_SCH_DEFAULT 359 menuconfig NET_SCH_DEFAULT
407 bool "Allow override default queue dis 360 bool "Allow override default queue discipline"
408 help !! 361 ---help---
409 Support for selection of default que 362 Support for selection of default queuing discipline.
410 363
411 Nearly all users can safely say no h 364 Nearly all users can safely say no here, and the default
412 of pfifo_fast will be used. Many dis 365 of pfifo_fast will be used. Many distributions already set
413 the default value via /proc/sys/net/ 366 the default value via /proc/sys/net/core/default_qdisc.
414 367
415 If unsure, say N. 368 If unsure, say N.
416 369
417 if NET_SCH_DEFAULT 370 if NET_SCH_DEFAULT
418 371
419 choice 372 choice
420 prompt "Default queuing discipline" 373 prompt "Default queuing discipline"
421 default DEFAULT_PFIFO_FAST 374 default DEFAULT_PFIFO_FAST
422 help 375 help
423 Select the queueing discipline that 376 Select the queueing discipline that will be used by default
424 for all network devices. 377 for all network devices.
425 378
426 config DEFAULT_FQ 379 config DEFAULT_FQ
427 bool "Fair Queue" if NET_SCH_F 380 bool "Fair Queue" if NET_SCH_FQ
428 381
429 config DEFAULT_CODEL 382 config DEFAULT_CODEL
430 bool "Controlled Delay" if NET 383 bool "Controlled Delay" if NET_SCH_CODEL
431 384
432 config DEFAULT_FQ_CODEL 385 config DEFAULT_FQ_CODEL
433 bool "Fair Queue Controlled De 386 bool "Fair Queue Controlled Delay" if NET_SCH_FQ_CODEL
434 387
435 config DEFAULT_FQ_PIE <<
436 bool "Flow Queue Proportional <<
437 <<
438 config DEFAULT_SFQ 388 config DEFAULT_SFQ
439 bool "Stochastic Fair Queue" i 389 bool "Stochastic Fair Queue" if NET_SCH_SFQ
440 390
441 config DEFAULT_PFIFO_FAST 391 config DEFAULT_PFIFO_FAST
442 bool "Priority FIFO Fast" 392 bool "Priority FIFO Fast"
443 endchoice 393 endchoice
444 394
445 config DEFAULT_NET_SCH 395 config DEFAULT_NET_SCH
446 string 396 string
447 default "pfifo_fast" if DEFAULT_PFIFO_ 397 default "pfifo_fast" if DEFAULT_PFIFO_FAST
448 default "fq" if DEFAULT_FQ 398 default "fq" if DEFAULT_FQ
449 default "fq_codel" if DEFAULT_FQ_CODEL 399 default "fq_codel" if DEFAULT_FQ_CODEL
450 default "fq_pie" if DEFAULT_FQ_PIE <<
451 default "sfq" if DEFAULT_SFQ 400 default "sfq" if DEFAULT_SFQ
452 default "pfifo_fast" 401 default "pfifo_fast"
453 endif 402 endif
454 403
455 comment "Classification" 404 comment "Classification"
456 405
457 config NET_CLS 406 config NET_CLS
458 bool 407 bool
459 408
460 config NET_CLS_BASIC 409 config NET_CLS_BASIC
461 tristate "Elementary classification (B 410 tristate "Elementary classification (BASIC)"
462 select NET_CLS 411 select NET_CLS
463 help !! 412 ---help---
464 Say Y here if you want to be able to 413 Say Y here if you want to be able to classify packets using
465 only extended matches and actions. 414 only extended matches and actions.
466 415
467 To compile this code as a module, ch 416 To compile this code as a module, choose M here: the
468 module will be called cls_basic. 417 module will be called cls_basic.
469 418
470 config NET_CLS_ROUTE4 419 config NET_CLS_ROUTE4
471 tristate "Routing decision (ROUTE)" 420 tristate "Routing decision (ROUTE)"
472 depends on INET 421 depends on INET
473 select IP_ROUTE_CLASSID 422 select IP_ROUTE_CLASSID
474 select NET_CLS 423 select NET_CLS
475 help !! 424 ---help---
476 If you say Y here, you will be able 425 If you say Y here, you will be able to classify packets
477 according to the route table entry t 426 according to the route table entry they matched.
478 427
479 To compile this code as a module, ch 428 To compile this code as a module, choose M here: the
480 module will be called cls_route. 429 module will be called cls_route.
481 430
482 config NET_CLS_FW 431 config NET_CLS_FW
483 tristate "Netfilter mark (FW)" 432 tristate "Netfilter mark (FW)"
484 select NET_CLS 433 select NET_CLS
485 help !! 434 ---help---
486 If you say Y here, you will be able 435 If you say Y here, you will be able to classify packets
487 according to netfilter/firewall mark 436 according to netfilter/firewall marks.
488 437
489 To compile this code as a module, ch 438 To compile this code as a module, choose M here: the
490 module will be called cls_fw. 439 module will be called cls_fw.
491 440
492 config NET_CLS_U32 441 config NET_CLS_U32
493 tristate "Universal 32bit comparisons 442 tristate "Universal 32bit comparisons w/ hashing (U32)"
494 select NET_CLS 443 select NET_CLS
495 help !! 444 ---help---
496 Say Y here to be able to classify pa 445 Say Y here to be able to classify packets using a universal
497 32bit pieces based comparison scheme 446 32bit pieces based comparison scheme.
498 447
499 To compile this code as a module, ch 448 To compile this code as a module, choose M here: the
500 module will be called cls_u32. 449 module will be called cls_u32.
501 450
502 config CLS_U32_PERF 451 config CLS_U32_PERF
503 bool "Performance counters support" 452 bool "Performance counters support"
504 depends on NET_CLS_U32 453 depends on NET_CLS_U32
505 help !! 454 ---help---
506 Say Y here to make u32 gather additi 455 Say Y here to make u32 gather additional statistics useful for
507 fine tuning u32 classifiers. 456 fine tuning u32 classifiers.
508 457
509 config CLS_U32_MARK 458 config CLS_U32_MARK
510 bool "Netfilter marks support" 459 bool "Netfilter marks support"
511 depends on NET_CLS_U32 460 depends on NET_CLS_U32
512 help !! 461 ---help---
513 Say Y here to be able to use netfilt 462 Say Y here to be able to use netfilter marks as u32 key.
514 463
515 config NET_CLS_FLOW 464 config NET_CLS_FLOW
516 tristate "Flow classifier" 465 tristate "Flow classifier"
517 select NET_CLS 466 select NET_CLS
518 help !! 467 ---help---
519 If you say Y here, you will be able 468 If you say Y here, you will be able to classify packets based on
520 a configurable combination of packet 469 a configurable combination of packet keys. This is mostly useful
521 in combination with SFQ. 470 in combination with SFQ.
522 471
523 To compile this code as a module, ch 472 To compile this code as a module, choose M here: the
524 module will be called cls_flow. 473 module will be called cls_flow.
525 474
526 config NET_CLS_CGROUP 475 config NET_CLS_CGROUP
527 tristate "Control Group Classifier" 476 tristate "Control Group Classifier"
528 select NET_CLS 477 select NET_CLS
529 select CGROUP_NET_CLASSID 478 select CGROUP_NET_CLASSID
530 depends on CGROUPS 479 depends on CGROUPS
531 help !! 480 ---help---
532 Say Y here if you want to classify p 481 Say Y here if you want to classify packets based on the control
533 cgroup of their process. 482 cgroup of their process.
534 483
535 To compile this code as a module, ch 484 To compile this code as a module, choose M here: the
536 module will be called cls_cgroup. 485 module will be called cls_cgroup.
537 486
538 config NET_CLS_BPF 487 config NET_CLS_BPF
539 tristate "BPF-based classifier" 488 tristate "BPF-based classifier"
540 select NET_CLS 489 select NET_CLS
541 help !! 490 ---help---
542 If you say Y here, you will be able 491 If you say Y here, you will be able to classify packets based on
543 programmable BPF (JIT'ed) filters as 492 programmable BPF (JIT'ed) filters as an alternative to ematches.
544 493
545 To compile this code as a module, ch 494 To compile this code as a module, choose M here: the module will
546 be called cls_bpf. 495 be called cls_bpf.
547 496
548 config NET_CLS_FLOWER 497 config NET_CLS_FLOWER
549 tristate "Flower classifier" 498 tristate "Flower classifier"
550 select NET_CLS 499 select NET_CLS
551 help !! 500 ---help---
552 If you say Y here, you will be able 501 If you say Y here, you will be able to classify packets based on
553 a configurable combination of packet 502 a configurable combination of packet keys and masks.
554 503
555 To compile this code as a module, ch 504 To compile this code as a module, choose M here: the module will
556 be called cls_flower. 505 be called cls_flower.
557 506
558 config NET_CLS_MATCHALL 507 config NET_CLS_MATCHALL
559 tristate "Match-all classifier" 508 tristate "Match-all classifier"
560 select NET_CLS 509 select NET_CLS
561 help !! 510 ---help---
562 If you say Y here, you will be able 511 If you say Y here, you will be able to classify packets based on
563 nothing. Every packet will match. 512 nothing. Every packet will match.
564 513
565 To compile this code as a module, ch 514 To compile this code as a module, choose M here: the module will
566 be called cls_matchall. 515 be called cls_matchall.
567 516
568 config NET_EMATCH 517 config NET_EMATCH
569 bool "Extended Matches" 518 bool "Extended Matches"
570 select NET_CLS 519 select NET_CLS
571 help !! 520 ---help---
572 Say Y here if you want to use extend 521 Say Y here if you want to use extended matches on top of classifiers
573 and select the extended matches belo 522 and select the extended matches below.
574 523
575 Extended matches are small classific 524 Extended matches are small classification helpers not worth writing
576 a separate classifier for. 525 a separate classifier for.
577 526
578 A recent version of the iproute2 pac 527 A recent version of the iproute2 package is required to use
579 extended matches. 528 extended matches.
580 529
581 config NET_EMATCH_STACK 530 config NET_EMATCH_STACK
582 int "Stack size" 531 int "Stack size"
583 depends on NET_EMATCH 532 depends on NET_EMATCH
584 default "32" 533 default "32"
585 help !! 534 ---help---
586 Size of the local stack variable use 535 Size of the local stack variable used while evaluating the tree of
587 ematches. Limits the depth of the tr 536 ematches. Limits the depth of the tree, i.e. the number of
588 encapsulated precedences. Every leve 537 encapsulated precedences. Every level requires 4 bytes of additional
589 stack space. 538 stack space.
590 539
591 config NET_EMATCH_CMP 540 config NET_EMATCH_CMP
592 tristate "Simple packet data compariso 541 tristate "Simple packet data comparison"
593 depends on NET_EMATCH 542 depends on NET_EMATCH
594 help !! 543 ---help---
595 Say Y here if you want to be able to 544 Say Y here if you want to be able to classify packets based on
596 simple packet data comparisons for 8 545 simple packet data comparisons for 8, 16, and 32bit values.
597 546
598 To compile this code as a module, ch 547 To compile this code as a module, choose M here: the
599 module will be called em_cmp. 548 module will be called em_cmp.
600 549
601 config NET_EMATCH_NBYTE 550 config NET_EMATCH_NBYTE
602 tristate "Multi byte comparison" 551 tristate "Multi byte comparison"
603 depends on NET_EMATCH 552 depends on NET_EMATCH
604 help !! 553 ---help---
605 Say Y here if you want to be able to 554 Say Y here if you want to be able to classify packets based on
606 multiple byte comparisons mainly use 555 multiple byte comparisons mainly useful for IPv6 address comparisons.
607 556
608 To compile this code as a module, ch 557 To compile this code as a module, choose M here: the
609 module will be called em_nbyte. 558 module will be called em_nbyte.
610 559
611 config NET_EMATCH_U32 560 config NET_EMATCH_U32
612 tristate "U32 key" 561 tristate "U32 key"
613 depends on NET_EMATCH 562 depends on NET_EMATCH
614 help !! 563 ---help---
615 Say Y here if you want to be able to 564 Say Y here if you want to be able to classify packets using
616 the famous u32 key in combination wi 565 the famous u32 key in combination with logic relations.
617 566
618 To compile this code as a module, ch 567 To compile this code as a module, choose M here: the
619 module will be called em_u32. 568 module will be called em_u32.
620 569
621 config NET_EMATCH_META 570 config NET_EMATCH_META
622 tristate "Metadata" 571 tristate "Metadata"
623 depends on NET_EMATCH 572 depends on NET_EMATCH
624 help !! 573 ---help---
625 Say Y here if you want to be able to 574 Say Y here if you want to be able to classify packets based on
626 metadata such as load average, netfi 575 metadata such as load average, netfilter attributes, socket
627 attributes and routing decisions. 576 attributes and routing decisions.
628 577
629 To compile this code as a module, ch 578 To compile this code as a module, choose M here: the
630 module will be called em_meta. 579 module will be called em_meta.
631 580
632 config NET_EMATCH_TEXT 581 config NET_EMATCH_TEXT
633 tristate "Textsearch" 582 tristate "Textsearch"
634 depends on NET_EMATCH 583 depends on NET_EMATCH
635 select TEXTSEARCH 584 select TEXTSEARCH
636 select TEXTSEARCH_KMP 585 select TEXTSEARCH_KMP
637 select TEXTSEARCH_BM 586 select TEXTSEARCH_BM
638 select TEXTSEARCH_FSM 587 select TEXTSEARCH_FSM
639 help !! 588 ---help---
640 Say Y here if you want to be able to 589 Say Y here if you want to be able to classify packets based on
641 textsearch comparisons. 590 textsearch comparisons.
642 591
643 To compile this code as a module, ch 592 To compile this code as a module, choose M here: the
644 module will be called em_text. 593 module will be called em_text.
645 594
646 config NET_EMATCH_CANID 595 config NET_EMATCH_CANID
647 tristate "CAN Identifier" 596 tristate "CAN Identifier"
648 depends on NET_EMATCH && (CAN=y || CAN 597 depends on NET_EMATCH && (CAN=y || CAN=m)
649 help !! 598 ---help---
650 Say Y here if you want to be able to 599 Say Y here if you want to be able to classify CAN frames based
651 on CAN Identifier. 600 on CAN Identifier.
652 601
653 To compile this code as a module, ch 602 To compile this code as a module, choose M here: the
654 module will be called em_canid. 603 module will be called em_canid.
655 604
656 config NET_EMATCH_IPSET 605 config NET_EMATCH_IPSET
657 tristate "IPset" 606 tristate "IPset"
658 depends on NET_EMATCH && IP_SET 607 depends on NET_EMATCH && IP_SET
659 help !! 608 ---help---
660 Say Y here if you want to be able to 609 Say Y here if you want to be able to classify packets based on
661 ipset membership. 610 ipset membership.
662 611
663 To compile this code as a module, ch 612 To compile this code as a module, choose M here: the
664 module will be called em_ipset. 613 module will be called em_ipset.
665 614
666 config NET_EMATCH_IPT 615 config NET_EMATCH_IPT
667 tristate "IPtables Matches" 616 tristate "IPtables Matches"
668 depends on NET_EMATCH && NETFILTER && 617 depends on NET_EMATCH && NETFILTER && NETFILTER_XTABLES
669 help !! 618 ---help---
670 Say Y here to be able to classify pa 619 Say Y here to be able to classify packets based on iptables
671 matches. 620 matches.
672 Current supported match is "policy" 621 Current supported match is "policy" which allows packet classification
673 based on IPsec policy that was used 622 based on IPsec policy that was used during decapsulation
674 623
675 To compile this code as a module, ch 624 To compile this code as a module, choose M here: the
676 module will be called em_ipt. 625 module will be called em_ipt.
677 626
678 config NET_CLS_ACT 627 config NET_CLS_ACT
679 bool "Actions" 628 bool "Actions"
680 select NET_CLS 629 select NET_CLS
681 select NET_XGRESS !! 630 ---help---
682 help <<
683 Say Y here if you want to use traffi 631 Say Y here if you want to use traffic control actions. Actions
684 get attached to classifiers and are 632 get attached to classifiers and are invoked after a successful
685 classification. They are used to ove 633 classification. They are used to overwrite the classification
686 result, instantly drop or redirect p 634 result, instantly drop or redirect packets, etc.
687 635
688 A recent version of the iproute2 pac 636 A recent version of the iproute2 package is required to use
689 extended matches. 637 extended matches.
690 638
691 config NET_ACT_POLICE 639 config NET_ACT_POLICE
692 tristate "Traffic Policing" 640 tristate "Traffic Policing"
693 depends on NET_CLS_ACT !! 641 depends on NET_CLS_ACT
694 help !! 642 ---help---
695 Say Y here if you want to do traffic 643 Say Y here if you want to do traffic policing, i.e. strict
696 bandwidth limiting. This action repl 644 bandwidth limiting. This action replaces the existing policing
697 module. 645 module.
698 646
699 To compile this code as a module, ch 647 To compile this code as a module, choose M here: the
700 module will be called act_police. 648 module will be called act_police.
701 649
702 config NET_ACT_GACT 650 config NET_ACT_GACT
703 tristate "Generic actions" !! 651 tristate "Generic actions"
704 depends on NET_CLS_ACT !! 652 depends on NET_CLS_ACT
705 help !! 653 ---help---
706 Say Y here to take generic actions s 654 Say Y here to take generic actions such as dropping and
707 accepting packets. 655 accepting packets.
708 656
709 To compile this code as a module, ch 657 To compile this code as a module, choose M here: the
710 module will be called act_gact. 658 module will be called act_gact.
711 659
712 config GACT_PROB 660 config GACT_PROB
713 bool "Probability support" !! 661 bool "Probability support"
714 depends on NET_ACT_GACT !! 662 depends on NET_ACT_GACT
715 help !! 663 ---help---
716 Say Y here to use the generic action 664 Say Y here to use the generic action randomly or deterministically.
717 665
718 config NET_ACT_MIRRED 666 config NET_ACT_MIRRED
719 tristate "Redirecting and Mirroring" !! 667 tristate "Redirecting and Mirroring"
720 depends on NET_CLS_ACT !! 668 depends on NET_CLS_ACT
721 help !! 669 ---help---
722 Say Y here to allow packets to be mi 670 Say Y here to allow packets to be mirrored or redirected to
723 other devices. 671 other devices.
724 672
725 To compile this code as a module, ch 673 To compile this code as a module, choose M here: the
726 module will be called act_mirred. 674 module will be called act_mirred.
727 675
728 config NET_ACT_SAMPLE 676 config NET_ACT_SAMPLE
729 tristate "Traffic Sampling" !! 677 tristate "Traffic Sampling"
730 depends on NET_CLS_ACT !! 678 depends on NET_CLS_ACT
731 select PSAMPLE !! 679 select PSAMPLE
732 help !! 680 ---help---
733 Say Y here to allow packet sampling 681 Say Y here to allow packet sampling tc action. The packet sample
734 action consists of statistically cho 682 action consists of statistically choosing packets and sampling
735 them using the psample module. 683 them using the psample module.
736 684
737 To compile this code as a module, ch 685 To compile this code as a module, choose M here: the
738 module will be called act_sample. 686 module will be called act_sample.
739 687
>> 688 config NET_ACT_IPT
>> 689 tristate "IPtables targets"
>> 690 depends on NET_CLS_ACT && NETFILTER && IP_NF_IPTABLES
>> 691 ---help---
>> 692 Say Y here to be able to invoke iptables targets after successful
>> 693 classification.
>> 694
>> 695 To compile this code as a module, choose M here: the
>> 696 module will be called act_ipt.
>> 697
740 config NET_ACT_NAT 698 config NET_ACT_NAT
741 tristate "Stateless NAT" !! 699 tristate "Stateless NAT"
742 depends on NET_CLS_ACT !! 700 depends on NET_CLS_ACT
743 help !! 701 ---help---
744 Say Y here to do stateless NAT on IP 702 Say Y here to do stateless NAT on IPv4 packets. You should use
745 netfilter for NAT unless you know wh 703 netfilter for NAT unless you know what you are doing.
746 704
747 To compile this code as a module, ch 705 To compile this code as a module, choose M here: the
748 module will be called act_nat. 706 module will be called act_nat.
749 707
750 config NET_ACT_PEDIT 708 config NET_ACT_PEDIT
751 tristate "Packet Editing" !! 709 tristate "Packet Editing"
752 depends on NET_CLS_ACT !! 710 depends on NET_CLS_ACT
753 help !! 711 ---help---
754 Say Y here if you want to mangle the 712 Say Y here if you want to mangle the content of packets.
755 713
756 To compile this code as a module, ch 714 To compile this code as a module, choose M here: the
757 module will be called act_pedit. 715 module will be called act_pedit.
758 716
759 config NET_ACT_SIMP 717 config NET_ACT_SIMP
760 tristate "Simple Example (Debug)" !! 718 tristate "Simple Example (Debug)"
761 depends on NET_CLS_ACT !! 719 depends on NET_CLS_ACT
762 help !! 720 ---help---
763 Say Y here to add a simple action fo 721 Say Y here to add a simple action for demonstration purposes.
764 It is meant as an example and for de 722 It is meant as an example and for debugging purposes. It will
765 print a configured policy string fol 723 print a configured policy string followed by the packet count
766 to the console for every packet that 724 to the console for every packet that passes by.
767 725
768 If unsure, say N. 726 If unsure, say N.
769 727
770 To compile this code as a module, ch 728 To compile this code as a module, choose M here: the
771 module will be called act_simple. 729 module will be called act_simple.
772 730
773 config NET_ACT_SKBEDIT 731 config NET_ACT_SKBEDIT
774 tristate "SKB Editing" !! 732 tristate "SKB Editing"
775 depends on NET_CLS_ACT !! 733 depends on NET_CLS_ACT
776 help !! 734 ---help---
777 Say Y here to change skb priority or 735 Say Y here to change skb priority or queue_mapping settings.
778 736
779 If unsure, say N. 737 If unsure, say N.
780 738
781 To compile this code as a module, ch 739 To compile this code as a module, choose M here: the
782 module will be called act_skbedit. 740 module will be called act_skbedit.
783 741
784 config NET_ACT_CSUM 742 config NET_ACT_CSUM
785 tristate "Checksum Updating" !! 743 tristate "Checksum Updating"
786 depends on NET_CLS_ACT && INET !! 744 depends on NET_CLS_ACT && INET
787 select LIBCRC32C !! 745 select LIBCRC32C
788 help !! 746 ---help---
789 Say Y here to update some common che 747 Say Y here to update some common checksum after some direct
790 packet alterations. 748 packet alterations.
791 749
792 To compile this code as a module, ch 750 To compile this code as a module, choose M here: the
793 module will be called act_csum. 751 module will be called act_csum.
794 752
795 config NET_ACT_MPLS <<
796 tristate "MPLS manipulation" <<
797 depends on NET_CLS_ACT <<
798 help <<
799 Say Y here to push or pop MPLS heade <<
800 <<
801 If unsure, say N. <<
802 <<
803 To compile this code as a module, ch <<
804 module will be called act_mpls. <<
805 <<
806 config NET_ACT_VLAN 753 config NET_ACT_VLAN
807 tristate "Vlan manipulation" !! 754 tristate "Vlan manipulation"
808 depends on NET_CLS_ACT !! 755 depends on NET_CLS_ACT
809 help !! 756 ---help---
810 Say Y here to push or pop vlan heade 757 Say Y here to push or pop vlan headers.
811 758
812 If unsure, say N. 759 If unsure, say N.
813 760
814 To compile this code as a module, ch 761 To compile this code as a module, choose M here: the
815 module will be called act_vlan. 762 module will be called act_vlan.
816 763
817 config NET_ACT_BPF 764 config NET_ACT_BPF
818 tristate "BPF based action" !! 765 tristate "BPF based action"
819 depends on NET_CLS_ACT !! 766 depends on NET_CLS_ACT
820 help !! 767 ---help---
821 Say Y here to execute BPF code on pa 768 Say Y here to execute BPF code on packets. The BPF code will decide
822 if the packet should be dropped or n 769 if the packet should be dropped or not.
823 770
824 If unsure, say N. 771 If unsure, say N.
825 772
826 To compile this code as a module, ch 773 To compile this code as a module, choose M here: the
827 module will be called act_bpf. 774 module will be called act_bpf.
828 775
829 config NET_ACT_CONNMARK 776 config NET_ACT_CONNMARK
830 tristate "Netfilter Connection Mark Re !! 777 tristate "Netfilter Connection Mark Retriever"
831 depends on NET_CLS_ACT && NETFILTER !! 778 depends on NET_CLS_ACT && NETFILTER && IP_NF_IPTABLES
832 depends on NF_CONNTRACK && NF_CONNTRAC !! 779 depends on NF_CONNTRACK && NF_CONNTRACK_MARK
833 help !! 780 ---help---
834 Say Y here to allow retrieving of co 781 Say Y here to allow retrieving of conn mark
835 782
836 If unsure, say N. 783 If unsure, say N.
837 784
838 To compile this code as a module, ch 785 To compile this code as a module, choose M here: the
839 module will be called act_connmark. 786 module will be called act_connmark.
840 787
841 config NET_ACT_CTINFO <<
842 tristate "Netfilter Connection Mark Ac <<
843 depends on NET_CLS_ACT && NETFILTER <<
844 depends on NF_CONNTRACK && NF_CONNTRAC <<
845 help <<
846 Say Y here to allow transfer of a co <<
847 Current actions transfer connmark st <<
848 ipv4/v6 diffserv and/or to transfer <<
849 mark. Both are useful for restoring <<
850 back onto ingress connections for qd <<
851 purposes. <<
852 <<
853 If unsure, say N. <<
854 <<
855 To compile this code as a module, ch <<
856 module will be called act_ctinfo. <<
857 <<
858 config NET_ACT_SKBMOD 788 config NET_ACT_SKBMOD
859 tristate "skb data modification action !! 789 tristate "skb data modification action"
860 depends on NET_CLS_ACT !! 790 depends on NET_CLS_ACT
861 help !! 791 ---help---
862 Say Y here to allow modification of s !! 792 Say Y here to allow modification of skb data
863 793
864 If unsure, say N. !! 794 If unsure, say N.
865 795
866 To compile this code as a module, cho !! 796 To compile this code as a module, choose M here: the
867 module will be called act_skbmod. !! 797 module will be called act_skbmod.
868 798
869 config NET_ACT_IFE 799 config NET_ACT_IFE
870 tristate "Inter-FE action based on IET !! 800 tristate "Inter-FE action based on IETF ForCES InterFE LFB"
871 depends on NET_CLS_ACT !! 801 depends on NET_CLS_ACT
872 select NET_IFE !! 802 select NET_IFE
873 help !! 803 ---help---
874 Say Y here to allow for sourcing and 804 Say Y here to allow for sourcing and terminating metadata
875 For details refer to netdev01 paper: 805 For details refer to netdev01 paper:
876 "Distributing Linux Traffic Control 806 "Distributing Linux Traffic Control Classifier-Action Subsystem"
877 Authors: Jamal Hadi Salim and Damas 807 Authors: Jamal Hadi Salim and Damascene M. Joachimpillai
878 808
879 To compile this code as a module, ch 809 To compile this code as a module, choose M here: the
880 module will be called act_ife. 810 module will be called act_ife.
881 811
882 config NET_ACT_TUNNEL_KEY 812 config NET_ACT_TUNNEL_KEY
883 tristate "IP tunnel metadata manipulat !! 813 tristate "IP tunnel metadata manipulation"
884 depends on NET_CLS_ACT !! 814 depends on NET_CLS_ACT
885 help !! 815 ---help---
886 Say Y here to set/release ip tunnel 816 Say Y here to set/release ip tunnel metadata.
887 817
888 If unsure, say N. 818 If unsure, say N.
889 819
890 To compile this code as a module, ch 820 To compile this code as a module, choose M here: the
891 module will be called act_tunnel_key 821 module will be called act_tunnel_key.
892 822
893 config NET_ACT_CT <<
894 tristate "connection tracking tc actio <<
895 depends on NET_CLS_ACT && NF_CONNTRACK <<
896 select NF_CONNTRACK_OVS <<
897 select NF_NAT_OVS if NF_NAT <<
898 help <<
899 Say Y here to allow sending the pack <<
900 <<
901 If unsure, say N. <<
902 <<
903 To compile this code as a module, ch <<
904 module will be called act_ct. <<
905 <<
906 config NET_ACT_GATE <<
907 tristate "Frame gate entry list contro <<
908 depends on NET_CLS_ACT <<
909 help <<
910 Say Y here to allow to control the i <<
911 specific time slot and be dropped at <<
912 the gate entry list. <<
913 <<
914 If unsure, say N. <<
915 To compile this code as a module, ch <<
916 module will be called act_gate. <<
917 <<
918 config NET_IFE_SKBMARK 823 config NET_IFE_SKBMARK
919 tristate "Support to encoding decoding !! 824 tristate "Support to encoding decoding skb mark on IFE action"
920 depends on NET_ACT_IFE !! 825 depends on NET_ACT_IFE
921 826
922 config NET_IFE_SKBPRIO 827 config NET_IFE_SKBPRIO
923 tristate "Support to encoding decoding !! 828 tristate "Support to encoding decoding skb prio on IFE action"
924 depends on NET_ACT_IFE !! 829 depends on NET_ACT_IFE
925 830
926 config NET_IFE_SKBTCINDEX 831 config NET_IFE_SKBTCINDEX
927 tristate "Support to encoding decoding !! 832 tristate "Support to encoding decoding skb tcindex on IFE action"
928 depends on NET_ACT_IFE !! 833 depends on NET_ACT_IFE
929 <<
930 config NET_TC_SKB_EXT <<
931 bool "TC recirculation support" <<
932 depends on NET_CLS_ACT <<
933 select SKB_EXTENSIONS <<
934 <<
935 help <<
936 Say Y here to allow tc chain misses <<
937 the correct recirc_id, and hardware <<
938 the correct chain in tc software dat <<
939 834
940 Say N here if you won't be using tc< !! 835 config NET_CLS_IND
>> 836 bool "Incoming device classification"
>> 837 depends on NET_CLS_U32 || NET_CLS_FW
>> 838 ---help---
>> 839 Say Y here to extend the u32 and fw classifier to support
>> 840 classification based on the incoming device. This option is
>> 841 likely to disappear in favour of the metadata ematch.
941 842
942 endif # NET_SCHED 843 endif # NET_SCHED
943 844
944 config NET_SCH_FIFO 845 config NET_SCH_FIFO
945 bool 846 bool
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.