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