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 | ||
1da177e4 | 195 | config NET_SCH_NETEM |
52ab4ac2 | 196 | tristate "Network emulator (NETEM)" |
a7f7f624 | 197 | help |
1da177e4 LT |
198 | Say Y if you want to emulate network delay, loss, and packet |
199 | re-ordering. This is often useful to simulate networks when | |
200 | testing applications or protocols. | |
201 | ||
202 | To compile this driver as a module, choose M here: the module | |
203 | will be called sch_netem. | |
204 | ||
205 | If unsure, say N. | |
206 | ||
13d2a1d2 PM |
207 | config NET_SCH_DRR |
208 | tristate "Deficit Round Robin scheduler (DRR)" | |
209 | help | |
210 | Say Y here if you want to use the Deficit Round Robin (DRR) packet | |
211 | scheduling algorithm. | |
212 | ||
213 | To compile this driver as a module, choose M here: the module | |
214 | will be called sch_drr. | |
215 | ||
216 | If unsure, say N. | |
217 | ||
b8970f0b JF |
218 | config NET_SCH_MQPRIO |
219 | tristate "Multi-queue priority scheduler (MQPRIO)" | |
1dfe086d | 220 | select NET_SCH_MQPRIO_LIB |
b8970f0b JF |
221 | help |
222 | Say Y here if you want to use the Multi-queue Priority scheduler. | |
223 | This scheduler allows QOS to be offloaded on NICs that have support | |
224 | for offloading QOS schedulers. | |
225 | ||
226 | To compile this driver as a module, choose M here: the module will | |
227 | be called sch_mqprio. | |
228 | ||
229 | If unsure, say N. | |
230 | ||
aea5f654 ND |
231 | config NET_SCH_SKBPRIO |
232 | tristate "SKB priority queue scheduler (SKBPRIO)" | |
233 | help | |
234 | Say Y here if you want to use the SKB priority queue | |
235 | scheduler. This schedules packets according to skb->priority, | |
236 | which is useful for request packets in DoS mitigation systems such | |
237 | as Gatekeeper. | |
238 | ||
239 | To compile this driver as a module, choose M here: the module will | |
240 | be called sch_skbprio. | |
241 | ||
242 | If unsure, say N. | |
243 | ||
45e14433 | 244 | config NET_SCH_CHOKE |
245 | tristate "CHOose and Keep responsive flow scheduler (CHOKE)" | |
246 | help | |
247 | Say Y here if you want to use the CHOKe packet scheduler (CHOose | |
248 | and Keep for responsive flows, CHOose and Kill for unresponsive | |
8354bcbe | 249 | flows). This is a variation of RED which tries to penalize flows |
45e14433 | 250 | that monopolize the queue. |
251 | ||
252 | To compile this code as a module, choose M here: the | |
253 | module will be called sch_choke. | |
254 | ||
0545a303 | 255 | config NET_SCH_QFQ |
256 | tristate "Quick Fair Queueing scheduler (QFQ)" | |
257 | help | |
258 | Say Y here if you want to use the Quick Fair Queueing Scheduler (QFQ) | |
259 | packet scheduling algorithm. | |
260 | ||
261 | To compile this driver as a module, choose M here: the module | |
262 | will be called sch_qfq. | |
263 | ||
264 | If unsure, say N. | |
265 | ||
76e3cc12 ED |
266 | config NET_SCH_CODEL |
267 | tristate "Controlled Delay AQM (CODEL)" | |
268 | help | |
269 | Say Y here if you want to use the Controlled Delay (CODEL) | |
270 | packet scheduling algorithm. | |
271 | ||
272 | To compile this driver as a module, choose M here: the module | |
273 | will be called sch_codel. | |
274 | ||
275 | If unsure, say N. | |
276 | ||
4b549a2e ED |
277 | config NET_SCH_FQ_CODEL |
278 | tristate "Fair Queue Controlled Delay AQM (FQ_CODEL)" | |
279 | help | |
280 | Say Y here if you want to use the FQ Controlled Delay (FQ_CODEL) | |
281 | packet scheduling algorithm. | |
282 | ||
283 | To compile this driver as a module, choose M here: the module | |
284 | will be called sch_fq_codel. | |
285 | ||
286 | If unsure, say N. | |
287 | ||
046f6fd5 THJ |
288 | config NET_SCH_CAKE |
289 | tristate "Common Applications Kept Enhanced (CAKE)" | |
290 | help | |
291 | Say Y here if you want to use the Common Applications Kept Enhanced | |
bf69abad | 292 | (CAKE) queue management algorithm. |
046f6fd5 THJ |
293 | |
294 | To compile this driver as a module, choose M here: the module | |
295 | will be called sch_cake. | |
296 | ||
297 | If unsure, say N. | |
298 | ||
afe4fd06 ED |
299 | config NET_SCH_FQ |
300 | tristate "Fair Queue" | |
301 | help | |
302 | Say Y here if you want to use the FQ packet scheduling algorithm. | |
303 | ||
304 | FQ does flow separation, and is able to respect pacing requirements | |
6a7a2c18 | 305 | set by TCP stack into sk->sk_pacing_rate (for locally generated |
afe4fd06 ED |
306 | traffic) |
307 | ||
308 | To compile this driver as a module, choose M here: the module | |
309 | will be called sch_fq. | |
310 | ||
311 | If unsure, say N. | |
312 | ||
10239edf TL |
313 | config NET_SCH_HHF |
314 | tristate "Heavy-Hitter Filter (HHF)" | |
315 | help | |
316 | Say Y here if you want to use the Heavy-Hitter Filter (HHF) | |
317 | packet scheduling algorithm. | |
318 | ||
319 | To compile this driver as a module, choose M here: the module | |
320 | will be called sch_hhf. | |
321 | ||
d4b36210 VS |
322 | config NET_SCH_PIE |
323 | tristate "Proportional Integral controller Enhanced (PIE) scheduler" | |
324 | help | |
325 | Say Y here if you want to use the Proportional Integral controller | |
326 | Enhanced scheduler packet scheduling algorithm. | |
1f8389bf | 327 | For more information, please see https://tools.ietf.org/html/rfc8033 |
d4b36210 VS |
328 | |
329 | To compile this driver as a module, choose M here: the module | |
330 | will be called sch_pie. | |
331 | ||
332 | If unsure, say N. | |
333 | ||
ec97ecf1 MT |
334 | config NET_SCH_FQ_PIE |
335 | depends on NET_SCH_PIE | |
336 | tristate "Flow Queue Proportional Integral controller Enhanced (FQ-PIE)" | |
337 | help | |
338 | Say Y here if you want to use the Flow Queue Proportional Integral | |
339 | controller Enhanced (FQ-PIE) packet scheduling algorithm. | |
340 | For more information, please see https://tools.ietf.org/html/rfc8033 | |
341 | ||
342 | To compile this driver as a module, choose M here: the module | |
343 | will be called sch_fq_pie. | |
344 | ||
345 | If unsure, say N. | |
346 | ||
1da177e4 | 347 | config NET_SCH_INGRESS |
1f211a1b | 348 | tristate "Ingress/classifier-action Qdisc" |
72eb7bd2 | 349 | depends on NET_CLS_ACT |
1cf51900 | 350 | select NET_INGRESS |
1f211a1b | 351 | select NET_EGRESS |
a7f7f624 | 352 | help |
1f211a1b DB |
353 | Say Y here if you want to use classifiers for incoming and/or outgoing |
354 | packets. This qdisc doesn't do anything else besides running classifiers, | |
355 | which can also have actions attached to them. In case of outgoing packets, | |
356 | classifiers that this qdisc holds are executed in the transmit path | |
357 | before real enqueuing to an egress qdisc happens. | |
358 | ||
1da177e4 LT |
359 | If unsure, say Y. |
360 | ||
1f211a1b DB |
361 | To compile this code as a module, choose M here: the module will be |
362 | called sch_ingress with alias of sch_clsact. | |
1da177e4 | 363 | |
c3059be1 SR |
364 | config NET_SCH_PLUG |
365 | tristate "Plug network traffic until release (PLUG)" | |
a7f7f624 | 366 | help |
c3059be1 SR |
367 | |
368 | This queuing discipline allows userspace to plug/unplug a network | |
369 | output queue, using the netlink interface. When it receives an | |
370 | enqueue command it inserts a plug into the outbound queue that | |
371 | causes following packets to enqueue until a dequeue command arrives | |
372 | over netlink, causing the plug to be removed and resuming the normal | |
373 | packet flow. | |
374 | ||
375 | This module also provides a generic "network output buffering" | |
376 | functionality (aka output commit), wherein upon arrival of a dequeue | |
377 | command, only packets up to the first plug are released for delivery. | |
378 | The Remus HA project uses this module to enable speculative execution | |
379 | of virtual machines by allowing the generated network output to be rolled | |
380 | back if needed. | |
381 | ||
5d330cdd | 382 | For more information, please refer to <http://wiki.xenproject.org/wiki/Remus> |
c3059be1 SR |
383 | |
384 | Say Y here if you are using this kernel for Xen dom0 and | |
385 | want to protect Xen guests with Remus. | |
386 | ||
387 | To compile this code as a module, choose M here: the | |
388 | module will be called sch_plug. | |
389 | ||
dcc68b4d PM |
390 | config NET_SCH_ETS |
391 | tristate "Enhanced transmission selection scheduler (ETS)" | |
392 | help | |
393 | The Enhanced Transmission Selection scheduler is a classful | |
394 | queuing discipline that merges functionality of PRIO and DRR | |
395 | qdiscs in one scheduler. ETS makes it easy to configure a set of | |
396 | strict and bandwidth-sharing bands to implement the transmission | |
397 | selection described in 802.1Qaz. | |
398 | ||
399 | Say Y here if you want to use the ETS packet scheduling | |
400 | algorithm. | |
401 | ||
402 | To compile this driver as a module, choose M here: the module | |
403 | will be called sch_ets. | |
404 | ||
405 | If unsure, say N. | |
406 | ||
8ea3e439 | 407 | menuconfig NET_SCH_DEFAULT |
408 | bool "Allow override default queue discipline" | |
a7f7f624 | 409 | help |
8ea3e439 | 410 | Support for selection of default queuing discipline. |
411 | ||
412 | Nearly all users can safely say no here, and the default | |
413 | of pfifo_fast will be used. Many distributions already set | |
414 | the default value via /proc/sys/net/core/default_qdisc. | |
415 | ||
416 | If unsure, say N. | |
417 | ||
418 | if NET_SCH_DEFAULT | |
419 | ||
420 | choice | |
421 | prompt "Default queuing discipline" | |
422 | default DEFAULT_PFIFO_FAST | |
423 | help | |
424 | Select the queueing discipline that will be used by default | |
425 | for all network devices. | |
426 | ||
427 | config DEFAULT_FQ | |
428 | bool "Fair Queue" if NET_SCH_FQ | |
429 | ||
430 | config DEFAULT_CODEL | |
431 | bool "Controlled Delay" if NET_SCH_CODEL | |
432 | ||
433 | config DEFAULT_FQ_CODEL | |
434 | bool "Fair Queue Controlled Delay" if NET_SCH_FQ_CODEL | |
435 | ||
b97e9d9d DL |
436 | config DEFAULT_FQ_PIE |
437 | bool "Flow Queue Proportional Integral controller Enhanced" if NET_SCH_FQ_PIE | |
438 | ||
8ea3e439 | 439 | config DEFAULT_SFQ |
440 | bool "Stochastic Fair Queue" if NET_SCH_SFQ | |
441 | ||
442 | config DEFAULT_PFIFO_FAST | |
443 | bool "Priority FIFO Fast" | |
444 | endchoice | |
445 | ||
446 | config DEFAULT_NET_SCH | |
447 | string | |
448 | default "pfifo_fast" if DEFAULT_PFIFO_FAST | |
449 | default "fq" if DEFAULT_FQ | |
450 | default "fq_codel" if DEFAULT_FQ_CODEL | |
b97e9d9d | 451 | default "fq_pie" if DEFAULT_FQ_PIE |
8ea3e439 | 452 | default "sfq" if DEFAULT_SFQ |
453 | default "pfifo_fast" | |
454 | endif | |
455 | ||
52ab4ac2 | 456 | comment "Classification" |
1da177e4 LT |
457 | |
458 | config NET_CLS | |
6341e62b | 459 | bool |
1da177e4 LT |
460 | |
461 | config NET_CLS_BASIC | |
52ab4ac2 | 462 | tristate "Elementary classification (BASIC)" |
52ab4ac2 | 463 | select NET_CLS |
a7f7f624 | 464 | help |
1da177e4 LT |
465 | Say Y here if you want to be able to classify packets using |
466 | only extended matches and actions. | |
467 | ||
468 | To compile this code as a module, choose M here: the | |
469 | module will be called cls_basic. | |
470 | ||
1da177e4 | 471 | config NET_CLS_ROUTE4 |
52ab4ac2 | 472 | tristate "Routing decision (ROUTE)" |
034cfe48 | 473 | depends on INET |
c7066f70 | 474 | select IP_ROUTE_CLASSID |
52ab4ac2 | 475 | select NET_CLS |
a7f7f624 | 476 | help |
52ab4ac2 TG |
477 | If you say Y here, you will be able to classify packets |
478 | according to the route table entry they matched. | |
1da177e4 LT |
479 | |
480 | To compile this code as a module, choose M here: the | |
481 | module will be called cls_route. | |
482 | ||
1da177e4 | 483 | config NET_CLS_FW |
52ab4ac2 | 484 | tristate "Netfilter mark (FW)" |
52ab4ac2 | 485 | select NET_CLS |
a7f7f624 | 486 | help |
52ab4ac2 TG |
487 | If you say Y here, you will be able to classify packets |
488 | according to netfilter/firewall marks. | |
1da177e4 LT |
489 | |
490 | To compile this code as a module, choose M here: the | |
491 | module will be called cls_fw. | |
492 | ||
493 | config NET_CLS_U32 | |
52ab4ac2 | 494 | tristate "Universal 32bit comparisons w/ hashing (U32)" |
52ab4ac2 | 495 | select NET_CLS |
a7f7f624 | 496 | help |
3539c272 | 497 | Say Y here to be able to classify packets using a universal |
52ab4ac2 | 498 | 32bit pieces based comparison scheme. |
1da177e4 LT |
499 | |
500 | To compile this code as a module, choose M here: the | |
501 | module will be called cls_u32. | |
502 | ||
503 | config CLS_U32_PERF | |
52ab4ac2 | 504 | bool "Performance counters support" |
1da177e4 | 505 | depends on NET_CLS_U32 |
a7f7f624 | 506 | help |
52ab4ac2 TG |
507 | Say Y here to make u32 gather additional statistics useful for |
508 | fine tuning u32 classifiers. | |
1da177e4 LT |
509 | |
510 | config CLS_U32_MARK | |
52ab4ac2 | 511 | bool "Netfilter marks support" |
82e91ffe | 512 | depends on NET_CLS_U32 |
a7f7f624 | 513 | help |
52ab4ac2 | 514 | Say Y here to be able to use netfilter marks as u32 key. |
1da177e4 | 515 | |
e5dfb815 PM |
516 | config NET_CLS_FLOW |
517 | tristate "Flow classifier" | |
518 | select NET_CLS | |
a7f7f624 | 519 | help |
e5dfb815 PM |
520 | If you say Y here, you will be able to classify packets based on |
521 | a configurable combination of packet keys. This is mostly useful | |
522 | in combination with SFQ. | |
523 | ||
524 | To compile this code as a module, choose M here: the | |
525 | module will be called cls_flow. | |
526 | ||
f4009237 | 527 | config NET_CLS_CGROUP |
8e039d84 | 528 | tristate "Control Group Classifier" |
f4009237 | 529 | select NET_CLS |
fe1217c4 | 530 | select CGROUP_NET_CLASSID |
f4009237 | 531 | depends on CGROUPS |
a7f7f624 | 532 | help |
f4009237 TG |
533 | Say Y here if you want to classify packets based on the control |
534 | cgroup of their process. | |
535 | ||
8e039d84 BB |
536 | To compile this code as a module, choose M here: the |
537 | module will be called cls_cgroup. | |
538 | ||
7d1d65cb DB |
539 | config NET_CLS_BPF |
540 | tristate "BPF-based classifier" | |
541 | select NET_CLS | |
a7f7f624 | 542 | help |
7d1d65cb DB |
543 | If you say Y here, you will be able to classify packets based on |
544 | programmable BPF (JIT'ed) filters as an alternative to ematches. | |
545 | ||
546 | To compile this code as a module, choose M here: the module will | |
547 | be called cls_bpf. | |
548 | ||
77b9900e JP |
549 | config NET_CLS_FLOWER |
550 | tristate "Flower classifier" | |
551 | select NET_CLS | |
a7f7f624 | 552 | help |
77b9900e JP |
553 | If you say Y here, you will be able to classify packets based on |
554 | a configurable combination of packet keys and masks. | |
555 | ||
556 | To compile this code as a module, choose M here: the module will | |
557 | be called cls_flower. | |
558 | ||
bf3994d2 JP |
559 | config NET_CLS_MATCHALL |
560 | tristate "Match-all classifier" | |
561 | select NET_CLS | |
a7f7f624 | 562 | help |
bf3994d2 JP |
563 | If you say Y here, you will be able to classify packets based on |
564 | nothing. Every packet will match. | |
565 | ||
566 | To compile this code as a module, choose M here: the module will | |
567 | be called cls_matchall. | |
568 | ||
1da177e4 LT |
569 | config NET_EMATCH |
570 | bool "Extended Matches" | |
52ab4ac2 | 571 | select NET_CLS |
a7f7f624 | 572 | help |
1da177e4 LT |
573 | Say Y here if you want to use extended matches on top of classifiers |
574 | and select the extended matches below. | |
575 | ||
576 | Extended matches are small classification helpers not worth writing | |
52ab4ac2 | 577 | a separate classifier for. |
1da177e4 | 578 | |
52ab4ac2 | 579 | A recent version of the iproute2 package is required to use |
1da177e4 LT |
580 | extended matches. |
581 | ||
582 | config NET_EMATCH_STACK | |
583 | int "Stack size" | |
584 | depends on NET_EMATCH | |
585 | default "32" | |
a7f7f624 | 586 | help |
1da177e4 LT |
587 | Size of the local stack variable used while evaluating the tree of |
588 | ematches. Limits the depth of the tree, i.e. the number of | |
b824979a | 589 | encapsulated precedences. Every level requires 4 bytes of additional |
1da177e4 LT |
590 | stack space. |
591 | ||
592 | config NET_EMATCH_CMP | |
593 | tristate "Simple packet data comparison" | |
594 | depends on NET_EMATCH | |
a7f7f624 | 595 | help |
1da177e4 LT |
596 | Say Y here if you want to be able to classify packets based on |
597 | simple packet data comparisons for 8, 16, and 32bit values. | |
598 | ||
599 | To compile this code as a module, choose M here: the | |
600 | module will be called em_cmp. | |
601 | ||
602 | config NET_EMATCH_NBYTE | |
603 | tristate "Multi byte comparison" | |
604 | depends on NET_EMATCH | |
a7f7f624 | 605 | help |
1da177e4 LT |
606 | Say Y here if you want to be able to classify packets based on |
607 | multiple byte comparisons mainly useful for IPv6 address comparisons. | |
608 | ||
609 | To compile this code as a module, choose M here: the | |
610 | module will be called em_nbyte. | |
611 | ||
612 | config NET_EMATCH_U32 | |
52ab4ac2 | 613 | tristate "U32 key" |
1da177e4 | 614 | depends on NET_EMATCH |
a7f7f624 | 615 | help |
1da177e4 LT |
616 | Say Y here if you want to be able to classify packets using |
617 | the famous u32 key in combination with logic relations. | |
618 | ||
619 | To compile this code as a module, choose M here: the | |
620 | module will be called em_u32. | |
621 | ||
622 | config NET_EMATCH_META | |
623 | tristate "Metadata" | |
624 | depends on NET_EMATCH | |
a7f7f624 | 625 | help |
bb7e8c5a | 626 | Say Y here if you want to be able to classify packets based on |
1da177e4 LT |
627 | metadata such as load average, netfilter attributes, socket |
628 | attributes and routing decisions. | |
629 | ||
630 | To compile this code as a module, choose M here: the | |
631 | module will be called em_meta. | |
632 | ||
d675c989 TG |
633 | config NET_EMATCH_TEXT |
634 | tristate "Textsearch" | |
635 | depends on NET_EMATCH | |
f2d368fa | 636 | select TEXTSEARCH |
f7704347 | 637 | select TEXTSEARCH_KMP |
29cb9f9c | 638 | select TEXTSEARCH_BM |
f7704347 | 639 | select TEXTSEARCH_FSM |
a7f7f624 | 640 | help |
52ab4ac2 | 641 | Say Y here if you want to be able to classify packets based on |
f7704347 | 642 | textsearch comparisons. |
d675c989 TG |
643 | |
644 | To compile this code as a module, choose M here: the | |
645 | module will be called em_text. | |
646 | ||
f057bbb6 RL |
647 | config NET_EMATCH_CANID |
648 | tristate "CAN Identifier" | |
a303fbf3 | 649 | depends on NET_EMATCH && (CAN=y || CAN=m) |
a7f7f624 | 650 | help |
f057bbb6 RL |
651 | Say Y here if you want to be able to classify CAN frames based |
652 | on CAN Identifier. | |
653 | ||
654 | To compile this code as a module, choose M here: the | |
655 | module will be called em_canid. | |
656 | ||
6d4fa852 FW |
657 | config NET_EMATCH_IPSET |
658 | tristate "IPset" | |
659 | depends on NET_EMATCH && IP_SET | |
a7f7f624 | 660 | help |
6d4fa852 FW |
661 | Say Y here if you want to be able to classify packets based on |
662 | ipset membership. | |
663 | ||
664 | To compile this code as a module, choose M here: the | |
665 | module will be called em_ipset. | |
666 | ||
ccc007e4 EB |
667 | config NET_EMATCH_IPT |
668 | tristate "IPtables Matches" | |
669 | depends on NET_EMATCH && NETFILTER && NETFILTER_XTABLES | |
a7f7f624 | 670 | help |
ccc007e4 EB |
671 | Say Y here to be able to classify packets based on iptables |
672 | matches. | |
673 | Current supported match is "policy" which allows packet classification | |
674 | based on IPsec policy that was used during decapsulation | |
675 | ||
676 | To compile this code as a module, choose M here: the | |
677 | module will be called em_ipt. | |
678 | ||
1da177e4 | 679 | config NET_CLS_ACT |
52ab4ac2 | 680 | bool "Actions" |
8ec1507d | 681 | select NET_CLS |
a7f7f624 | 682 | help |
52ab4ac2 TG |
683 | Say Y here if you want to use traffic control actions. Actions |
684 | get attached to classifiers and are invoked after a successful | |
685 | classification. They are used to overwrite the classification | |
686 | result, instantly drop or redirect packets, etc. | |
687 | ||
688 | A recent version of the iproute2 package is required to use | |
689 | extended matches. | |
1da177e4 LT |
690 | |
691 | config NET_ACT_POLICE | |
52ab4ac2 | 692 | tristate "Traffic Policing" |
bf69abad | 693 | depends on NET_CLS_ACT |
a7f7f624 | 694 | help |
52ab4ac2 TG |
695 | Say Y here if you want to do traffic policing, i.e. strict |
696 | bandwidth limiting. This action replaces the existing policing | |
697 | module. | |
698 | ||
699 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 700 | module will be called act_police. |
1da177e4 LT |
701 | |
702 | config NET_ACT_GACT | |
bf69abad KK |
703 | tristate "Generic actions" |
704 | depends on NET_CLS_ACT | |
a7f7f624 | 705 | help |
52ab4ac2 TG |
706 | Say Y here to take generic actions such as dropping and |
707 | accepting packets. | |
708 | ||
709 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 710 | module will be called act_gact. |
1da177e4 LT |
711 | |
712 | config GACT_PROB | |
bf69abad KK |
713 | bool "Probability support" |
714 | depends on NET_ACT_GACT | |
a7f7f624 | 715 | help |
52ab4ac2 | 716 | Say Y here to use the generic action randomly or deterministically. |
1da177e4 LT |
717 | |
718 | config NET_ACT_MIRRED | |
bf69abad KK |
719 | tristate "Redirecting and Mirroring" |
720 | depends on NET_CLS_ACT | |
a7f7f624 | 721 | help |
52ab4ac2 TG |
722 | Say Y here to allow packets to be mirrored or redirected to |
723 | other devices. | |
724 | ||
725 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 726 | module will be called act_mirred. |
1da177e4 | 727 | |
5c5670fa | 728 | config NET_ACT_SAMPLE |
bf69abad KK |
729 | tristate "Traffic Sampling" |
730 | depends on NET_CLS_ACT | |
731 | select PSAMPLE | |
a7f7f624 | 732 | help |
5c5670fa YG |
733 | Say Y here to allow packet sampling tc action. The packet sample |
734 | action consists of statistically choosing packets and sampling | |
735 | them using the psample module. | |
736 | ||
737 | To compile this code as a module, choose M here: the | |
738 | module will be called act_sample. | |
739 | ||
1da177e4 | 740 | config NET_ACT_IPT |
bf69abad | 741 | tristate "IPtables targets" |
102e2c07 | 742 | depends on NET_CLS_ACT && NETFILTER && NETFILTER_XTABLES |
a7f7f624 | 743 | help |
3539c272 | 744 | Say Y here to be able to invoke iptables targets after successful |
52ab4ac2 TG |
745 | classification. |
746 | ||
747 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 748 | module will be called act_ipt. |
1da177e4 | 749 | |
b4219952 | 750 | config NET_ACT_NAT |
bf69abad KK |
751 | tristate "Stateless NAT" |
752 | depends on NET_CLS_ACT | |
a7f7f624 | 753 | help |
b4219952 HX |
754 | Say Y here to do stateless NAT on IPv4 packets. You should use |
755 | netfilter for NAT unless you know what you are doing. | |
756 | ||
757 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 758 | module will be called act_nat. |
b4219952 | 759 | |
1da177e4 | 760 | config NET_ACT_PEDIT |
bf69abad KK |
761 | tristate "Packet Editing" |
762 | depends on NET_CLS_ACT | |
a7f7f624 | 763 | help |
52ab4ac2 | 764 | Say Y here if you want to mangle the content of packets. |
1da177e4 | 765 | |
52ab4ac2 | 766 | To compile this code as a module, choose M here: the |
d4ae20b3 | 767 | module will be called act_pedit. |
1da177e4 | 768 | |
db753079 | 769 | config NET_ACT_SIMP |
bf69abad KK |
770 | tristate "Simple Example (Debug)" |
771 | depends on NET_CLS_ACT | |
a7f7f624 | 772 | help |
52ab4ac2 TG |
773 | Say Y here to add a simple action for demonstration purposes. |
774 | It is meant as an example and for debugging purposes. It will | |
775 | print a configured policy string followed by the packet count | |
776 | to the console for every packet that passes by. | |
777 | ||
778 | If unsure, say N. | |
779 | ||
780 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 781 | module will be called act_simple. |
52ab4ac2 | 782 | |
ca9b0e27 | 783 | config NET_ACT_SKBEDIT |
bf69abad KK |
784 | tristate "SKB Editing" |
785 | depends on NET_CLS_ACT | |
a7f7f624 | 786 | help |
ca9b0e27 AD |
787 | Say Y here to change skb priority or queue_mapping settings. |
788 | ||
789 | If unsure, say N. | |
790 | ||
791 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 792 | module will be called act_skbedit. |
ca9b0e27 | 793 | |
eb4d4065 | 794 | config NET_ACT_CSUM |
bf69abad KK |
795 | tristate "Checksum Updating" |
796 | depends on NET_CLS_ACT && INET | |
797 | select LIBCRC32C | |
a7f7f624 | 798 | help |
eb4d4065 GB |
799 | Say Y here to update some common checksum after some direct |
800 | packet alterations. | |
801 | ||
802 | To compile this code as a module, choose M here: the | |
803 | module will be called act_csum. | |
804 | ||
2a2ea508 JH |
805 | config NET_ACT_MPLS |
806 | tristate "MPLS manipulation" | |
807 | depends on NET_CLS_ACT | |
808 | help | |
809 | Say Y here to push or pop MPLS headers. | |
810 | ||
811 | If unsure, say N. | |
812 | ||
813 | To compile this code as a module, choose M here: the | |
814 | module will be called act_mpls. | |
815 | ||
c7e2b968 | 816 | config NET_ACT_VLAN |
bf69abad KK |
817 | tristate "Vlan manipulation" |
818 | depends on NET_CLS_ACT | |
a7f7f624 | 819 | help |
c7e2b968 JP |
820 | Say Y here to push or pop vlan headers. |
821 | ||
822 | If unsure, say N. | |
823 | ||
824 | To compile this code as a module, choose M here: the | |
825 | module will be called act_vlan. | |
826 | ||
d23b8ad8 | 827 | config NET_ACT_BPF |
bf69abad KK |
828 | tristate "BPF based action" |
829 | depends on NET_CLS_ACT | |
a7f7f624 | 830 | help |
d23b8ad8 JP |
831 | Say Y here to execute BPF code on packets. The BPF code will decide |
832 | if the packet should be dropped or not. | |
833 | ||
834 | If unsure, say N. | |
835 | ||
836 | To compile this code as a module, choose M here: the | |
837 | module will be called act_bpf. | |
838 | ||
22a5dc0e | 839 | config NET_ACT_CONNMARK |
bf69abad | 840 | tristate "Netfilter Connection Mark Retriever" |
102e2c07 | 841 | depends on NET_CLS_ACT && NETFILTER |
bf69abad | 842 | depends on NF_CONNTRACK && NF_CONNTRACK_MARK |
a7f7f624 | 843 | help |
22a5dc0e FF |
844 | Say Y here to allow retrieving of conn mark |
845 | ||
846 | If unsure, say N. | |
847 | ||
848 | To compile this code as a module, choose M here: the | |
849 | module will be called act_connmark. | |
850 | ||
24ec483c | 851 | config NET_ACT_CTINFO |
bf69abad | 852 | tristate "Netfilter Connection Mark Actions" |
102e2c07 | 853 | depends on NET_CLS_ACT && NETFILTER |
bf69abad KK |
854 | depends on NF_CONNTRACK && NF_CONNTRACK_MARK |
855 | help | |
24ec483c KDB |
856 | Say Y here to allow transfer of a connmark stored information. |
857 | Current actions transfer connmark stored DSCP into | |
858 | ipv4/v6 diffserv and/or to transfer connmark to packet | |
859 | mark. Both are useful for restoring egress based marks | |
860 | back onto ingress connections for qdisc priority mapping | |
861 | purposes. | |
862 | ||
863 | If unsure, say N. | |
864 | ||
865 | To compile this code as a module, choose M here: the | |
866 | module will be called act_ctinfo. | |
867 | ||
86da71b5 | 868 | config NET_ACT_SKBMOD |
bf69abad KK |
869 | tristate "skb data modification action" |
870 | depends on NET_CLS_ACT | |
a7f7f624 | 871 | help |
bf69abad | 872 | Say Y here to allow modification of skb data |
86da71b5 | 873 | |
bf69abad | 874 | If unsure, say N. |
86da71b5 | 875 | |
bf69abad KK |
876 | To compile this code as a module, choose M here: the |
877 | module will be called act_skbmod. | |
86da71b5 | 878 | |
ef6980b6 | 879 | config NET_ACT_IFE |
bf69abad KK |
880 | tristate "Inter-FE action based on IETF ForCES InterFE LFB" |
881 | depends on NET_CLS_ACT | |
882 | select NET_IFE | |
a7f7f624 | 883 | help |
ef6980b6 JHS |
884 | Say Y here to allow for sourcing and terminating metadata |
885 | For details refer to netdev01 paper: | |
886 | "Distributing Linux Traffic Control Classifier-Action Subsystem" | |
887 | Authors: Jamal Hadi Salim and Damascene M. Joachimpillai | |
888 | ||
889 | To compile this code as a module, choose M here: the | |
890 | module will be called act_ife. | |
891 | ||
d0f6dd8a | 892 | config NET_ACT_TUNNEL_KEY |
bf69abad KK |
893 | tristate "IP tunnel metadata manipulation" |
894 | depends on NET_CLS_ACT | |
a7f7f624 | 895 | help |
d0f6dd8a AV |
896 | Say Y here to set/release ip tunnel metadata. |
897 | ||
898 | If unsure, say N. | |
899 | ||
900 | To compile this code as a module, choose M here: the | |
901 | module will be called act_tunnel_key. | |
902 | ||
b57dc7c1 | 903 | config NET_ACT_CT |
bf69abad | 904 | tristate "connection tracking tc action" |
8427fd10 | 905 | depends on NET_CLS_ACT && NF_CONNTRACK && (!NF_NAT || NF_NAT) && NF_FLOW_TABLE |
c0c3ab63 | 906 | select NF_CONNTRACK_OVS |
ebddb140 | 907 | select NF_NAT_OVS if NF_NAT |
bf69abad | 908 | help |
b57dc7c1 PB |
909 | Say Y here to allow sending the packets to conntrack module. |
910 | ||
911 | If unsure, say N. | |
912 | ||
913 | To compile this code as a module, choose M here: the | |
914 | module will be called act_ct. | |
915 | ||
a51c328d PL |
916 | config NET_ACT_GATE |
917 | tristate "Frame gate entry list control tc action" | |
918 | depends on NET_CLS_ACT | |
919 | help | |
920 | Say Y here to allow to control the ingress flow to be passed at | |
921 | specific time slot and be dropped at other specific time slot by | |
922 | the gate entry list. | |
923 | ||
924 | If unsure, say N. | |
925 | To compile this code as a module, choose M here: the | |
926 | module will be called act_gate. | |
927 | ||
084e2f65 | 928 | config NET_IFE_SKBMARK |
bf69abad KK |
929 | tristate "Support to encoding decoding skb mark on IFE action" |
930 | depends on NET_ACT_IFE | |
084e2f65 | 931 | |
200e10f4 | 932 | config NET_IFE_SKBPRIO |
bf69abad KK |
933 | tristate "Support to encoding decoding skb prio on IFE action" |
934 | depends on NET_ACT_IFE | |
200e10f4 | 935 | |
408fbc22 | 936 | config NET_IFE_SKBTCINDEX |
bf69abad KK |
937 | tristate "Support to encoding decoding skb tcindex on IFE action" |
938 | depends on NET_ACT_IFE | |
408fbc22 | 939 | |
95a7233c PB |
940 | config NET_TC_SKB_EXT |
941 | bool "TC recirculation support" | |
942 | depends on NET_CLS_ACT | |
95a7233c PB |
943 | select SKB_EXTENSIONS |
944 | ||
945 | help | |
946 | Say Y here to allow tc chain misses to continue in OvS datapath in | |
947 | the correct recirc_id, and hardware chain misses to continue in | |
948 | the correct chain in tc software datapath. | |
949 | ||
950 | Say N here if you won't be using tc<->ovs offload or tc chains offload. | |
951 | ||
05b8b0fa RZ |
952 | endif # NET_SCHED |
953 | ||
85ef3e5c RD |
954 | config NET_SCH_FIFO |
955 | bool |