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