]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Traffic control configuration. | |
3 | # | |
6a2e9b73 | 4 | |
85ef3e5c | 5 | menuconfig NET_SCHED |
6a2e9b73 | 6 | bool "QoS and/or fair queueing" |
3c62f75a | 7 | select NET_SCH_FIFO |
6a2e9b73 SR |
8 | ---help--- |
9 | When the kernel has several packets to send out over a network | |
10 | device, it has to decide which ones to send first, which ones to | |
52ab4ac2 TG |
11 | delay, and which ones to drop. This is the job of the queueing |
12 | disciplines, several different algorithms for how to do this | |
6a2e9b73 SR |
13 | "fairly" have been proposed. |
14 | ||
15 | If you say N here, you will get the standard packet scheduler, which | |
16 | is a FIFO (first come, first served). If you say Y here, you will be | |
17 | able to choose from among several alternative algorithms which can | |
18 | then be attached to different network devices. This is useful for | |
19 | example if some of your network devices are real time devices that | |
20 | need a certain minimum data flow rate, or if you need to limit the | |
21 | maximum data flow rate for traffic which matches specified criteria. | |
22 | This code is considered to be experimental. | |
23 | ||
24 | To administer these schedulers, you'll need the user-level utilities | |
25 | from the package iproute2+tc at <ftp://ftp.tux.org/pub/net/ip-routing/>. | |
26 | That package also contains some documentation; for more, check out | |
c996d8b9 | 27 | <http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2>. |
6a2e9b73 SR |
28 | |
29 | This Quality of Service (QoS) support will enable you to use | |
30 | Differentiated Services (diffserv) and Resource Reservation Protocol | |
52ab4ac2 TG |
31 | (RSVP) on your Linux router if you also say Y to the corresponding |
32 | classifiers below. Documentation and software is at | |
33 | <http://diffserv.sourceforge.net/>. | |
6a2e9b73 SR |
34 | |
35 | If you say Y here and to "/proc file system" below, you will be able | |
36 | to read status information about packet schedulers from the file | |
37 | /proc/net/psched. | |
38 | ||
39 | The available schedulers are listed in the following questions; you | |
40 | can say Y to as many as you like. If unsure, say N now. | |
41 | ||
05b8b0fa RZ |
42 | if NET_SCHED |
43 | ||
52ab4ac2 | 44 | comment "Queueing/Scheduling" |
52ab4ac2 | 45 | |
1da177e4 | 46 | config NET_SCH_CBQ |
52ab4ac2 | 47 | tristate "Class Based Queueing (CBQ)" |
1da177e4 LT |
48 | ---help--- |
49 | Say Y here if you want to use the Class-Based Queueing (CBQ) packet | |
52ab4ac2 TG |
50 | scheduling algorithm. This algorithm classifies the waiting packets |
51 | into a tree-like hierarchy of classes; the leaves of this tree are | |
52 | in turn scheduled by separate algorithms. | |
1da177e4 | 53 | |
52ab4ac2 | 54 | See the top of <file:net/sched/sch_cbq.c> for more details. |
1da177e4 LT |
55 | |
56 | CBQ is a commonly used scheduler, so if you're unsure, you should | |
57 | say Y here. Then say Y to all the queueing algorithms below that you | |
52ab4ac2 | 58 | want to use as leaf disciplines. |
1da177e4 LT |
59 | |
60 | To compile this code as a module, choose M here: the | |
61 | module will be called sch_cbq. | |
62 | ||
63 | config NET_SCH_HTB | |
52ab4ac2 | 64 | tristate "Hierarchical Token Bucket (HTB)" |
1da177e4 LT |
65 | ---help--- |
66 | Say Y here if you want to use the Hierarchical Token Buckets (HTB) | |
52ab4ac2 | 67 | packet scheduling algorithm. See |
1da177e4 LT |
68 | <http://luxik.cdi.cz/~devik/qos/htb/> for complete manual and |
69 | in-depth articles. | |
70 | ||
52ab4ac2 | 71 | HTB is very similar to CBQ regarding its goals however is has |
1da177e4 LT |
72 | different properties and different algorithm. |
73 | ||
74 | To compile this code as a module, choose M here: the | |
75 | module will be called sch_htb. | |
76 | ||
77 | config NET_SCH_HFSC | |
52ab4ac2 | 78 | tristate "Hierarchical Fair Service Curve (HFSC)" |
1da177e4 LT |
79 | ---help--- |
80 | Say Y here if you want to use the Hierarchical Fair Service Curve | |
52ab4ac2 | 81 | (HFSC) packet scheduling algorithm. |
1da177e4 LT |
82 | |
83 | To compile this code as a module, choose M here: the | |
84 | module will be called sch_hfsc. | |
85 | ||
1da177e4 | 86 | config NET_SCH_ATM |
52ab4ac2 | 87 | tristate "ATM Virtual Circuits (ATM)" |
05b8b0fa | 88 | depends on ATM |
1da177e4 LT |
89 | ---help--- |
90 | Say Y here if you want to use the ATM pseudo-scheduler. This | |
52ab4ac2 TG |
91 | provides a framework for invoking classifiers, which in turn |
92 | select classes of this queuing discipline. Each class maps | |
93 | the flow(s) it is handling to a given virtual circuit. | |
94 | ||
99acaeb9 | 95 | See the top of <file:net/sched/sch_atm.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_atm. | |
99 | ||
100 | config NET_SCH_PRIO | |
52ab4ac2 | 101 | tristate "Multi Band Priority Queueing (PRIO)" |
52ab4ac2 | 102 | ---help--- |
1da177e4 | 103 | Say Y here if you want to use an n-band priority queue packet |
52ab4ac2 | 104 | scheduler. |
1da177e4 LT |
105 | |
106 | To compile this code as a module, choose M here: the | |
107 | module will be called sch_prio. | |
108 | ||
92651940 AD |
109 | config NET_SCH_MULTIQ |
110 | tristate "Hardware Multiqueue-aware Multi Band Queuing (MULTIQ)" | |
111 | ---help--- | |
112 | Say Y here if you want to use an n-band queue packet scheduler | |
113 | to support devices that have multiple hardware transmit queues. | |
114 | ||
115 | To compile this code as a module, choose M here: the | |
116 | module will be called sch_multiq. | |
117 | ||
1da177e4 | 118 | config NET_SCH_RED |
52ab4ac2 | 119 | tristate "Random Early Detection (RED)" |
52ab4ac2 | 120 | ---help--- |
1da177e4 | 121 | Say Y here if you want to use the Random Early Detection (RED) |
52ab4ac2 TG |
122 | packet scheduling algorithm. |
123 | ||
124 | See the top of <file:net/sched/sch_red.c> for more details. | |
1da177e4 LT |
125 | |
126 | To compile this code as a module, choose M here: the | |
127 | module will be called sch_red. | |
128 | ||
e13e02a3 ED |
129 | config NET_SCH_SFB |
130 | tristate "Stochastic Fair Blue (SFB)" | |
131 | ---help--- | |
132 | Say Y here if you want to use the Stochastic Fair Blue (SFB) | |
133 | packet scheduling algorithm. | |
134 | ||
135 | See the top of <file:net/sched/sch_sfb.c> for more details. | |
136 | ||
137 | To compile this code as a module, choose M here: the | |
138 | module will be called sch_sfb. | |
139 | ||
1da177e4 | 140 | config NET_SCH_SFQ |
52ab4ac2 | 141 | tristate "Stochastic Fairness Queueing (SFQ)" |
1da177e4 LT |
142 | ---help--- |
143 | Say Y here if you want to use the Stochastic Fairness Queueing (SFQ) | |
99acaeb9 | 144 | packet scheduling algorithm. |
52ab4ac2 TG |
145 | |
146 | See the top of <file:net/sched/sch_sfq.c> for more details. | |
1da177e4 LT |
147 | |
148 | To compile this code as a module, choose M here: the | |
149 | module will be called sch_sfq. | |
150 | ||
151 | config NET_SCH_TEQL | |
52ab4ac2 | 152 | tristate "True Link Equalizer (TEQL)" |
1da177e4 LT |
153 | ---help--- |
154 | Say Y here if you want to use the True Link Equalizer (TLE) packet | |
52ab4ac2 TG |
155 | scheduling algorithm. This queueing discipline allows the combination |
156 | of several physical devices into one virtual device. | |
157 | ||
158 | See the top of <file:net/sched/sch_teql.c> for more details. | |
1da177e4 LT |
159 | |
160 | To compile this code as a module, choose M here: the | |
161 | module will be called sch_teql. | |
162 | ||
163 | config NET_SCH_TBF | |
52ab4ac2 | 164 | tristate "Token Bucket Filter (TBF)" |
52ab4ac2 TG |
165 | ---help--- |
166 | Say Y here if you want to use the Token Bucket Filter (TBF) packet | |
167 | scheduling algorithm. | |
168 | ||
169 | See the top of <file:net/sched/sch_tbf.c> for more details. | |
1da177e4 LT |
170 | |
171 | To compile this code as a module, choose M here: the | |
172 | module will be called sch_tbf. | |
173 | ||
174 | config NET_SCH_GRED | |
52ab4ac2 | 175 | tristate "Generic Random Early Detection (GRED)" |
52ab4ac2 | 176 | ---help--- |
1da177e4 | 177 | Say Y here if you want to use the Generic Random Early Detection |
20cc6bef | 178 | (GRED) packet scheduling algorithm for some of your network devices |
1da177e4 LT |
179 | (see the top of <file:net/sched/sch_red.c> for details and |
180 | references about the algorithm). | |
181 | ||
182 | To compile this code as a module, choose M here: the | |
183 | module will be called sch_gred. | |
184 | ||
185 | config NET_SCH_DSMARK | |
52ab4ac2 | 186 | tristate "Differentiated Services marker (DSMARK)" |
52ab4ac2 | 187 | ---help--- |
1da177e4 LT |
188 | Say Y if you want to schedule packets according to the |
189 | Differentiated Services architecture proposed in RFC 2475. | |
190 | Technical information on this method, with pointers to associated | |
191 | RFCs, is available at <http://www.gta.ufrj.br/diffserv/>. | |
192 | ||
193 | To compile this code as a module, choose M here: the | |
194 | module will be called sch_dsmark. | |
195 | ||
196 | config NET_SCH_NETEM | |
52ab4ac2 | 197 | tristate "Network emulator (NETEM)" |
52ab4ac2 | 198 | ---help--- |
1da177e4 LT |
199 | Say Y if you want to emulate network delay, loss, and packet |
200 | re-ordering. This is often useful to simulate networks when | |
201 | testing applications or protocols. | |
202 | ||
203 | To compile this driver as a module, choose M here: the module | |
204 | will be called sch_netem. | |
205 | ||
206 | If unsure, say N. | |
207 | ||
13d2a1d2 PM |
208 | config NET_SCH_DRR |
209 | tristate "Deficit Round Robin scheduler (DRR)" | |
210 | help | |
211 | Say Y here if you want to use the Deficit Round Robin (DRR) packet | |
212 | scheduling algorithm. | |
213 | ||
214 | To compile this driver as a module, choose M here: the module | |
215 | will be called sch_drr. | |
216 | ||
217 | If unsure, say N. | |
218 | ||
b8970f0b JF |
219 | config NET_SCH_MQPRIO |
220 | tristate "Multi-queue priority scheduler (MQPRIO)" | |
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 | ||
45e14433 | 231 | config NET_SCH_CHOKE |
232 | tristate "CHOose and Keep responsive flow scheduler (CHOKE)" | |
233 | help | |
234 | Say Y here if you want to use the CHOKe packet scheduler (CHOose | |
235 | and Keep for responsive flows, CHOose and Kill for unresponsive | |
236 | flows). This is a variation of RED which trys to penalize flows | |
237 | that monopolize the queue. | |
238 | ||
239 | To compile this code as a module, choose M here: the | |
240 | module will be called sch_choke. | |
241 | ||
0545a303 | 242 | config NET_SCH_QFQ |
243 | tristate "Quick Fair Queueing scheduler (QFQ)" | |
244 | help | |
245 | Say Y here if you want to use the Quick Fair Queueing Scheduler (QFQ) | |
246 | packet scheduling algorithm. | |
247 | ||
248 | To compile this driver as a module, choose M here: the module | |
249 | will be called sch_qfq. | |
250 | ||
251 | If unsure, say N. | |
252 | ||
76e3cc12 ED |
253 | config NET_SCH_CODEL |
254 | tristate "Controlled Delay AQM (CODEL)" | |
255 | help | |
256 | Say Y here if you want to use the Controlled Delay (CODEL) | |
257 | packet scheduling algorithm. | |
258 | ||
259 | To compile this driver as a module, choose M here: the module | |
260 | will be called sch_codel. | |
261 | ||
262 | If unsure, say N. | |
263 | ||
4b549a2e ED |
264 | config NET_SCH_FQ_CODEL |
265 | tristate "Fair Queue Controlled Delay AQM (FQ_CODEL)" | |
266 | help | |
267 | Say Y here if you want to use the FQ Controlled Delay (FQ_CODEL) | |
268 | packet scheduling algorithm. | |
269 | ||
270 | To compile this driver as a module, choose M here: the module | |
271 | will be called sch_fq_codel. | |
272 | ||
273 | If unsure, say N. | |
274 | ||
1da177e4 LT |
275 | config NET_SCH_INGRESS |
276 | tristate "Ingress Qdisc" | |
72eb7bd2 | 277 | depends on NET_CLS_ACT |
52ab4ac2 TG |
278 | ---help--- |
279 | Say Y here if you want to use classifiers for incoming packets. | |
1da177e4 LT |
280 | If unsure, say Y. |
281 | ||
282 | To compile this code as a module, choose M here: the | |
283 | module will be called sch_ingress. | |
284 | ||
c3059be1 SR |
285 | config NET_SCH_PLUG |
286 | tristate "Plug network traffic until release (PLUG)" | |
287 | ---help--- | |
288 | ||
289 | This queuing discipline allows userspace to plug/unplug a network | |
290 | output queue, using the netlink interface. When it receives an | |
291 | enqueue command it inserts a plug into the outbound queue that | |
292 | causes following packets to enqueue until a dequeue command arrives | |
293 | over netlink, causing the plug to be removed and resuming the normal | |
294 | packet flow. | |
295 | ||
296 | This module also provides a generic "network output buffering" | |
297 | functionality (aka output commit), wherein upon arrival of a dequeue | |
298 | command, only packets up to the first plug are released for delivery. | |
299 | The Remus HA project uses this module to enable speculative execution | |
300 | of virtual machines by allowing the generated network output to be rolled | |
301 | back if needed. | |
302 | ||
303 | For more information, please refer to http://wiki.xensource.com/xenwiki/Remus | |
304 | ||
305 | Say Y here if you are using this kernel for Xen dom0 and | |
306 | want to protect Xen guests with Remus. | |
307 | ||
308 | To compile this code as a module, choose M here: the | |
309 | module will be called sch_plug. | |
310 | ||
52ab4ac2 | 311 | comment "Classification" |
1da177e4 LT |
312 | |
313 | config NET_CLS | |
52ab4ac2 | 314 | boolean |
1da177e4 LT |
315 | |
316 | config NET_CLS_BASIC | |
52ab4ac2 | 317 | tristate "Elementary classification (BASIC)" |
52ab4ac2 | 318 | select NET_CLS |
1da177e4 LT |
319 | ---help--- |
320 | Say Y here if you want to be able to classify packets using | |
321 | only extended matches and actions. | |
322 | ||
323 | To compile this code as a module, choose M here: the | |
324 | module will be called cls_basic. | |
325 | ||
326 | config NET_CLS_TCINDEX | |
52ab4ac2 | 327 | tristate "Traffic-Control Index (TCINDEX)" |
52ab4ac2 TG |
328 | select NET_CLS |
329 | ---help--- | |
330 | Say Y here if you want to be able to classify packets based on | |
331 | traffic control indices. You will want this feature if you want | |
332 | to implement Differentiated Services together with DSMARK. | |
1da177e4 LT |
333 | |
334 | To compile this code as a module, choose M here: the | |
335 | module will be called cls_tcindex. | |
336 | ||
337 | config NET_CLS_ROUTE4 | |
52ab4ac2 | 338 | tristate "Routing decision (ROUTE)" |
034cfe48 | 339 | depends on INET |
c7066f70 | 340 | select IP_ROUTE_CLASSID |
52ab4ac2 TG |
341 | select NET_CLS |
342 | ---help--- | |
343 | If you say Y here, you will be able to classify packets | |
344 | according to the route table entry they matched. | |
1da177e4 LT |
345 | |
346 | To compile this code as a module, choose M here: the | |
347 | module will be called cls_route. | |
348 | ||
1da177e4 | 349 | config NET_CLS_FW |
52ab4ac2 | 350 | tristate "Netfilter mark (FW)" |
52ab4ac2 TG |
351 | select NET_CLS |
352 | ---help--- | |
353 | If you say Y here, you will be able to classify packets | |
354 | according to netfilter/firewall marks. | |
1da177e4 LT |
355 | |
356 | To compile this code as a module, choose M here: the | |
357 | module will be called cls_fw. | |
358 | ||
359 | config NET_CLS_U32 | |
52ab4ac2 | 360 | tristate "Universal 32bit comparisons w/ hashing (U32)" |
52ab4ac2 TG |
361 | select NET_CLS |
362 | ---help--- | |
3539c272 | 363 | Say Y here to be able to classify packets using a universal |
52ab4ac2 | 364 | 32bit pieces based comparison scheme. |
1da177e4 LT |
365 | |
366 | To compile this code as a module, choose M here: the | |
367 | module will be called cls_u32. | |
368 | ||
369 | config CLS_U32_PERF | |
52ab4ac2 | 370 | bool "Performance counters support" |
1da177e4 | 371 | depends on NET_CLS_U32 |
52ab4ac2 TG |
372 | ---help--- |
373 | Say Y here to make u32 gather additional statistics useful for | |
374 | fine tuning u32 classifiers. | |
1da177e4 LT |
375 | |
376 | config CLS_U32_MARK | |
52ab4ac2 | 377 | bool "Netfilter marks support" |
82e91ffe | 378 | depends on NET_CLS_U32 |
52ab4ac2 TG |
379 | ---help--- |
380 | Say Y here to be able to use netfilter marks as u32 key. | |
1da177e4 LT |
381 | |
382 | config NET_CLS_RSVP | |
52ab4ac2 | 383 | tristate "IPv4 Resource Reservation Protocol (RSVP)" |
52ab4ac2 | 384 | select NET_CLS |
1da177e4 LT |
385 | ---help--- |
386 | The Resource Reservation Protocol (RSVP) permits end systems to | |
387 | request a minimum and maximum data flow rate for a connection; this | |
388 | is important for real time data such as streaming sound or video. | |
389 | ||
390 | Say Y here if you want to be able to classify outgoing packets based | |
391 | on their RSVP requests. | |
392 | ||
393 | To compile this code as a module, choose M here: the | |
394 | module will be called cls_rsvp. | |
395 | ||
396 | config NET_CLS_RSVP6 | |
52ab4ac2 | 397 | tristate "IPv6 Resource Reservation Protocol (RSVP6)" |
52ab4ac2 | 398 | select NET_CLS |
1da177e4 LT |
399 | ---help--- |
400 | The Resource Reservation Protocol (RSVP) permits end systems to | |
401 | request a minimum and maximum data flow rate for a connection; this | |
402 | is important for real time data such as streaming sound or video. | |
403 | ||
404 | Say Y here if you want to be able to classify outgoing packets based | |
99acaeb9 | 405 | on their RSVP requests and you are using the IPv6 protocol. |
1da177e4 LT |
406 | |
407 | To compile this code as a module, choose M here: the | |
408 | module will be called cls_rsvp6. | |
409 | ||
e5dfb815 PM |
410 | config NET_CLS_FLOW |
411 | tristate "Flow classifier" | |
412 | select NET_CLS | |
413 | ---help--- | |
414 | If you say Y here, you will be able to classify packets based on | |
415 | a configurable combination of packet keys. This is mostly useful | |
416 | in combination with SFQ. | |
417 | ||
418 | To compile this code as a module, choose M here: the | |
419 | module will be called cls_flow. | |
420 | ||
f4009237 | 421 | config NET_CLS_CGROUP |
8e039d84 | 422 | tristate "Control Group Classifier" |
f4009237 TG |
423 | select NET_CLS |
424 | depends on CGROUPS | |
425 | ---help--- | |
426 | Say Y here if you want to classify packets based on the control | |
427 | cgroup of their process. | |
428 | ||
8e039d84 BB |
429 | To compile this code as a module, choose M here: the |
430 | module will be called cls_cgroup. | |
431 | ||
1da177e4 LT |
432 | config NET_EMATCH |
433 | bool "Extended Matches" | |
52ab4ac2 | 434 | select NET_CLS |
1da177e4 LT |
435 | ---help--- |
436 | Say Y here if you want to use extended matches on top of classifiers | |
437 | and select the extended matches below. | |
438 | ||
439 | Extended matches are small classification helpers not worth writing | |
52ab4ac2 | 440 | a separate classifier for. |
1da177e4 | 441 | |
52ab4ac2 | 442 | A recent version of the iproute2 package is required to use |
1da177e4 LT |
443 | extended matches. |
444 | ||
445 | config NET_EMATCH_STACK | |
446 | int "Stack size" | |
447 | depends on NET_EMATCH | |
448 | default "32" | |
449 | ---help--- | |
450 | Size of the local stack variable used while evaluating the tree of | |
451 | ematches. Limits the depth of the tree, i.e. the number of | |
b824979a | 452 | encapsulated precedences. Every level requires 4 bytes of additional |
1da177e4 LT |
453 | stack space. |
454 | ||
455 | config NET_EMATCH_CMP | |
456 | tristate "Simple packet data comparison" | |
457 | depends on NET_EMATCH | |
458 | ---help--- | |
459 | Say Y here if you want to be able to classify packets based on | |
460 | simple packet data comparisons for 8, 16, and 32bit values. | |
461 | ||
462 | To compile this code as a module, choose M here: the | |
463 | module will be called em_cmp. | |
464 | ||
465 | config NET_EMATCH_NBYTE | |
466 | tristate "Multi byte comparison" | |
467 | depends on NET_EMATCH | |
468 | ---help--- | |
469 | Say Y here if you want to be able to classify packets based on | |
470 | multiple byte comparisons mainly useful for IPv6 address comparisons. | |
471 | ||
472 | To compile this code as a module, choose M here: the | |
473 | module will be called em_nbyte. | |
474 | ||
475 | config NET_EMATCH_U32 | |
52ab4ac2 | 476 | tristate "U32 key" |
1da177e4 LT |
477 | depends on NET_EMATCH |
478 | ---help--- | |
479 | Say Y here if you want to be able to classify packets using | |
480 | the famous u32 key in combination with logic relations. | |
481 | ||
482 | To compile this code as a module, choose M here: the | |
483 | module will be called em_u32. | |
484 | ||
485 | config NET_EMATCH_META | |
486 | tristate "Metadata" | |
487 | depends on NET_EMATCH | |
488 | ---help--- | |
bb7e8c5a | 489 | Say Y here if you want to be able to classify packets based on |
1da177e4 LT |
490 | metadata such as load average, netfilter attributes, socket |
491 | attributes and routing decisions. | |
492 | ||
493 | To compile this code as a module, choose M here: the | |
494 | module will be called em_meta. | |
495 | ||
d675c989 TG |
496 | config NET_EMATCH_TEXT |
497 | tristate "Textsearch" | |
498 | depends on NET_EMATCH | |
f2d368fa | 499 | select TEXTSEARCH |
f7704347 | 500 | select TEXTSEARCH_KMP |
29cb9f9c | 501 | select TEXTSEARCH_BM |
f7704347 | 502 | select TEXTSEARCH_FSM |
d675c989 | 503 | ---help--- |
52ab4ac2 | 504 | Say Y here if you want to be able to classify packets based on |
f7704347 | 505 | textsearch comparisons. |
d675c989 TG |
506 | |
507 | To compile this code as a module, choose M here: the | |
508 | module will be called em_text. | |
509 | ||
f057bbb6 RL |
510 | config NET_EMATCH_CANID |
511 | tristate "CAN Identifier" | |
a303fbf3 | 512 | depends on NET_EMATCH && (CAN=y || CAN=m) |
f057bbb6 RL |
513 | ---help--- |
514 | Say Y here if you want to be able to classify CAN frames based | |
515 | on CAN Identifier. | |
516 | ||
517 | To compile this code as a module, choose M here: the | |
518 | module will be called em_canid. | |
519 | ||
6d4fa852 FW |
520 | config NET_EMATCH_IPSET |
521 | tristate "IPset" | |
522 | depends on NET_EMATCH && IP_SET | |
523 | ---help--- | |
524 | Say Y here if you want to be able to classify packets based on | |
525 | ipset membership. | |
526 | ||
527 | To compile this code as a module, choose M here: the | |
528 | module will be called em_ipset. | |
529 | ||
1da177e4 | 530 | config NET_CLS_ACT |
52ab4ac2 | 531 | bool "Actions" |
1da177e4 | 532 | ---help--- |
52ab4ac2 TG |
533 | Say Y here if you want to use traffic control actions. Actions |
534 | get attached to classifiers and are invoked after a successful | |
535 | classification. They are used to overwrite the classification | |
536 | result, instantly drop or redirect packets, etc. | |
537 | ||
538 | A recent version of the iproute2 package is required to use | |
539 | extended matches. | |
1da177e4 LT |
540 | |
541 | config NET_ACT_POLICE | |
52ab4ac2 | 542 | tristate "Traffic Policing" |
1da177e4 LT |
543 | depends on NET_CLS_ACT |
544 | ---help--- | |
52ab4ac2 TG |
545 | Say Y here if you want to do traffic policing, i.e. strict |
546 | bandwidth limiting. This action replaces the existing policing | |
547 | module. | |
548 | ||
549 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 550 | module will be called act_police. |
1da177e4 LT |
551 | |
552 | config NET_ACT_GACT | |
52ab4ac2 | 553 | tristate "Generic actions" |
1da177e4 LT |
554 | depends on NET_CLS_ACT |
555 | ---help--- | |
52ab4ac2 TG |
556 | Say Y here to take generic actions such as dropping and |
557 | accepting packets. | |
558 | ||
559 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 560 | module will be called act_gact. |
1da177e4 LT |
561 | |
562 | config GACT_PROB | |
52ab4ac2 | 563 | bool "Probability support" |
1da177e4 LT |
564 | depends on NET_ACT_GACT |
565 | ---help--- | |
52ab4ac2 | 566 | Say Y here to use the generic action randomly or deterministically. |
1da177e4 LT |
567 | |
568 | config NET_ACT_MIRRED | |
52ab4ac2 | 569 | tristate "Redirecting and Mirroring" |
1da177e4 LT |
570 | depends on NET_CLS_ACT |
571 | ---help--- | |
52ab4ac2 TG |
572 | Say Y here to allow packets to be mirrored or redirected to |
573 | other devices. | |
574 | ||
575 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 576 | module will be called act_mirred. |
1da177e4 LT |
577 | |
578 | config NET_ACT_IPT | |
52ab4ac2 | 579 | tristate "IPtables targets" |
1da177e4 LT |
580 | depends on NET_CLS_ACT && NETFILTER && IP_NF_IPTABLES |
581 | ---help--- | |
3539c272 | 582 | Say Y here to be able to invoke iptables targets after successful |
52ab4ac2 TG |
583 | classification. |
584 | ||
585 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 586 | module will be called act_ipt. |
1da177e4 | 587 | |
b4219952 HX |
588 | config NET_ACT_NAT |
589 | tristate "Stateless NAT" | |
590 | depends on NET_CLS_ACT | |
b4219952 HX |
591 | ---help--- |
592 | Say Y here to do stateless NAT on IPv4 packets. You should use | |
593 | netfilter for NAT unless you know what you are doing. | |
594 | ||
595 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 596 | module will be called act_nat. |
b4219952 | 597 | |
1da177e4 | 598 | config NET_ACT_PEDIT |
52ab4ac2 | 599 | tristate "Packet Editing" |
1da177e4 LT |
600 | depends on NET_CLS_ACT |
601 | ---help--- | |
52ab4ac2 | 602 | Say Y here if you want to mangle the content of packets. |
1da177e4 | 603 | |
52ab4ac2 | 604 | To compile this code as a module, choose M here: the |
d4ae20b3 | 605 | module will be called act_pedit. |
1da177e4 | 606 | |
db753079 | 607 | config NET_ACT_SIMP |
52ab4ac2 | 608 | tristate "Simple Example (Debug)" |
db753079 JHS |
609 | depends on NET_CLS_ACT |
610 | ---help--- | |
52ab4ac2 TG |
611 | Say Y here to add a simple action for demonstration purposes. |
612 | It is meant as an example and for debugging purposes. It will | |
613 | print a configured policy string followed by the packet count | |
614 | to the console for every packet that passes by. | |
615 | ||
616 | If unsure, say N. | |
617 | ||
618 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 619 | module will be called act_simple. |
52ab4ac2 | 620 | |
ca9b0e27 AD |
621 | config NET_ACT_SKBEDIT |
622 | tristate "SKB Editing" | |
623 | depends on NET_CLS_ACT | |
624 | ---help--- | |
625 | Say Y here to change skb priority or queue_mapping settings. | |
626 | ||
627 | If unsure, say N. | |
628 | ||
629 | To compile this code as a module, choose M here: the | |
d4ae20b3 | 630 | module will be called act_skbedit. |
ca9b0e27 | 631 | |
eb4d4065 GB |
632 | config NET_ACT_CSUM |
633 | tristate "Checksum Updating" | |
7abac686 | 634 | depends on NET_CLS_ACT && INET |
eb4d4065 GB |
635 | ---help--- |
636 | Say Y here to update some common checksum after some direct | |
637 | packet alterations. | |
638 | ||
639 | To compile this code as a module, choose M here: the | |
640 | module will be called act_csum. | |
641 | ||
52ab4ac2 TG |
642 | config NET_CLS_IND |
643 | bool "Incoming device classification" | |
05b8b0fa | 644 | depends on NET_CLS_U32 || NET_CLS_FW |
52ab4ac2 TG |
645 | ---help--- |
646 | Say Y here to extend the u32 and fw classifier to support | |
647 | classification based on the incoming device. This option is | |
648 | likely to disappear in favour of the metadata ematch. | |
649 | ||
05b8b0fa RZ |
650 | endif # NET_SCHED |
651 | ||
85ef3e5c RD |
652 | config NET_SCH_FIFO |
653 | bool |