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 | |
52ab4ac2 | 27 | <http://linux-net.osdl.org/index.php/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 | ||
129 | config NET_SCH_SFQ | |
52ab4ac2 | 130 | tristate "Stochastic Fairness Queueing (SFQ)" |
1da177e4 LT |
131 | ---help--- |
132 | Say Y here if you want to use the Stochastic Fairness Queueing (SFQ) | |
99acaeb9 | 133 | packet scheduling algorithm. |
52ab4ac2 TG |
134 | |
135 | See the top of <file:net/sched/sch_sfq.c> for more details. | |
1da177e4 LT |
136 | |
137 | To compile this code as a module, choose M here: the | |
138 | module will be called sch_sfq. | |
139 | ||
140 | config NET_SCH_TEQL | |
52ab4ac2 | 141 | tristate "True Link Equalizer (TEQL)" |
1da177e4 LT |
142 | ---help--- |
143 | Say Y here if you want to use the True Link Equalizer (TLE) packet | |
52ab4ac2 TG |
144 | scheduling algorithm. This queueing discipline allows the combination |
145 | of several physical devices into one virtual device. | |
146 | ||
147 | See the top of <file:net/sched/sch_teql.c> for more details. | |
1da177e4 LT |
148 | |
149 | To compile this code as a module, choose M here: the | |
150 | module will be called sch_teql. | |
151 | ||
152 | config NET_SCH_TBF | |
52ab4ac2 | 153 | tristate "Token Bucket Filter (TBF)" |
52ab4ac2 TG |
154 | ---help--- |
155 | Say Y here if you want to use the Token Bucket Filter (TBF) packet | |
156 | scheduling algorithm. | |
157 | ||
158 | See the top of <file:net/sched/sch_tbf.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_tbf. | |
162 | ||
163 | config NET_SCH_GRED | |
52ab4ac2 | 164 | tristate "Generic Random Early Detection (GRED)" |
52ab4ac2 | 165 | ---help--- |
1da177e4 | 166 | Say Y here if you want to use the Generic Random Early Detection |
20cc6bef | 167 | (GRED) packet scheduling algorithm for some of your network devices |
1da177e4 LT |
168 | (see the top of <file:net/sched/sch_red.c> for details and |
169 | references about the algorithm). | |
170 | ||
171 | To compile this code as a module, choose M here: the | |
172 | module will be called sch_gred. | |
173 | ||
174 | config NET_SCH_DSMARK | |
52ab4ac2 | 175 | tristate "Differentiated Services marker (DSMARK)" |
52ab4ac2 | 176 | ---help--- |
1da177e4 LT |
177 | Say Y if you want to schedule packets according to the |
178 | Differentiated Services architecture proposed in RFC 2475. | |
179 | Technical information on this method, with pointers to associated | |
180 | RFCs, is available at <http://www.gta.ufrj.br/diffserv/>. | |
181 | ||
182 | To compile this code as a module, choose M here: the | |
183 | module will be called sch_dsmark. | |
184 | ||
185 | config NET_SCH_NETEM | |
52ab4ac2 | 186 | tristate "Network emulator (NETEM)" |
52ab4ac2 | 187 | ---help--- |
1da177e4 LT |
188 | Say Y if you want to emulate network delay, loss, and packet |
189 | re-ordering. This is often useful to simulate networks when | |
190 | testing applications or protocols. | |
191 | ||
192 | To compile this driver as a module, choose M here: the module | |
193 | will be called sch_netem. | |
194 | ||
195 | If unsure, say N. | |
196 | ||
13d2a1d2 PM |
197 | config NET_SCH_DRR |
198 | tristate "Deficit Round Robin scheduler (DRR)" | |
199 | help | |
200 | Say Y here if you want to use the Deficit Round Robin (DRR) packet | |
201 | scheduling algorithm. | |
202 | ||
203 | To compile this driver as a module, choose M here: the module | |
204 | will be called sch_drr. | |
205 | ||
206 | If unsure, say N. | |
207 | ||
1da177e4 LT |
208 | config NET_SCH_INGRESS |
209 | tristate "Ingress Qdisc" | |
72eb7bd2 | 210 | depends on NET_CLS_ACT |
52ab4ac2 TG |
211 | ---help--- |
212 | Say Y here if you want to use classifiers for incoming packets. | |
1da177e4 LT |
213 | If unsure, say Y. |
214 | ||
215 | To compile this code as a module, choose M here: the | |
216 | module will be called sch_ingress. | |
217 | ||
52ab4ac2 | 218 | comment "Classification" |
1da177e4 LT |
219 | |
220 | config NET_CLS | |
52ab4ac2 | 221 | boolean |
1da177e4 LT |
222 | |
223 | config NET_CLS_BASIC | |
52ab4ac2 | 224 | tristate "Elementary classification (BASIC)" |
52ab4ac2 | 225 | select NET_CLS |
1da177e4 LT |
226 | ---help--- |
227 | Say Y here if you want to be able to classify packets using | |
228 | only extended matches and actions. | |
229 | ||
230 | To compile this code as a module, choose M here: the | |
231 | module will be called cls_basic. | |
232 | ||
233 | config NET_CLS_TCINDEX | |
52ab4ac2 | 234 | tristate "Traffic-Control Index (TCINDEX)" |
52ab4ac2 TG |
235 | select NET_CLS |
236 | ---help--- | |
237 | Say Y here if you want to be able to classify packets based on | |
238 | traffic control indices. You will want this feature if you want | |
239 | to implement Differentiated Services together with DSMARK. | |
1da177e4 LT |
240 | |
241 | To compile this code as a module, choose M here: the | |
242 | module will be called cls_tcindex. | |
243 | ||
244 | config NET_CLS_ROUTE4 | |
52ab4ac2 | 245 | tristate "Routing decision (ROUTE)" |
1da177e4 | 246 | select NET_CLS_ROUTE |
52ab4ac2 TG |
247 | select NET_CLS |
248 | ---help--- | |
249 | If you say Y here, you will be able to classify packets | |
250 | according to the route table entry they matched. | |
1da177e4 LT |
251 | |
252 | To compile this code as a module, choose M here: the | |
253 | module will be called cls_route. | |
254 | ||
255 | config NET_CLS_ROUTE | |
256 | bool | |
1da177e4 LT |
257 | |
258 | config NET_CLS_FW | |
52ab4ac2 | 259 | tristate "Netfilter mark (FW)" |
52ab4ac2 TG |
260 | select NET_CLS |
261 | ---help--- | |
262 | If you say Y here, you will be able to classify packets | |
263 | according to netfilter/firewall marks. | |
1da177e4 LT |
264 | |
265 | To compile this code as a module, choose M here: the | |
266 | module will be called cls_fw. | |
267 | ||
268 | config NET_CLS_U32 | |
52ab4ac2 | 269 | tristate "Universal 32bit comparisons w/ hashing (U32)" |
52ab4ac2 TG |
270 | select NET_CLS |
271 | ---help--- | |
3539c272 | 272 | Say Y here to be able to classify packets using a universal |
52ab4ac2 | 273 | 32bit pieces based comparison scheme. |
1da177e4 LT |
274 | |
275 | To compile this code as a module, choose M here: the | |
276 | module will be called cls_u32. | |
277 | ||
278 | config CLS_U32_PERF | |
52ab4ac2 | 279 | bool "Performance counters support" |
1da177e4 | 280 | depends on NET_CLS_U32 |
52ab4ac2 TG |
281 | ---help--- |
282 | Say Y here to make u32 gather additional statistics useful for | |
283 | fine tuning u32 classifiers. | |
1da177e4 LT |
284 | |
285 | config CLS_U32_MARK | |
52ab4ac2 | 286 | bool "Netfilter marks support" |
82e91ffe | 287 | depends on NET_CLS_U32 |
52ab4ac2 TG |
288 | ---help--- |
289 | Say Y here to be able to use netfilter marks as u32 key. | |
1da177e4 LT |
290 | |
291 | config NET_CLS_RSVP | |
52ab4ac2 | 292 | tristate "IPv4 Resource Reservation Protocol (RSVP)" |
52ab4ac2 | 293 | select NET_CLS |
1da177e4 LT |
294 | ---help--- |
295 | The Resource Reservation Protocol (RSVP) permits end systems to | |
296 | request a minimum and maximum data flow rate for a connection; this | |
297 | is important for real time data such as streaming sound or video. | |
298 | ||
299 | Say Y here if you want to be able to classify outgoing packets based | |
300 | on their RSVP requests. | |
301 | ||
302 | To compile this code as a module, choose M here: the | |
303 | module will be called cls_rsvp. | |
304 | ||
305 | config NET_CLS_RSVP6 | |
52ab4ac2 | 306 | tristate "IPv6 Resource Reservation Protocol (RSVP6)" |
52ab4ac2 | 307 | select NET_CLS |
1da177e4 LT |
308 | ---help--- |
309 | The Resource Reservation Protocol (RSVP) permits end systems to | |
310 | request a minimum and maximum data flow rate for a connection; this | |
311 | is important for real time data such as streaming sound or video. | |
312 | ||
313 | Say Y here if you want to be able to classify outgoing packets based | |
99acaeb9 | 314 | on their RSVP requests and you are using the IPv6 protocol. |
1da177e4 LT |
315 | |
316 | To compile this code as a module, choose M here: the | |
317 | module will be called cls_rsvp6. | |
318 | ||
e5dfb815 PM |
319 | config NET_CLS_FLOW |
320 | tristate "Flow classifier" | |
321 | select NET_CLS | |
322 | ---help--- | |
323 | If you say Y here, you will be able to classify packets based on | |
324 | a configurable combination of packet keys. This is mostly useful | |
325 | in combination with SFQ. | |
326 | ||
327 | To compile this code as a module, choose M here: the | |
328 | module will be called cls_flow. | |
329 | ||
f4009237 TG |
330 | config NET_CLS_CGROUP |
331 | bool "Control Group Classifier" | |
332 | select NET_CLS | |
333 | depends on CGROUPS | |
334 | ---help--- | |
335 | Say Y here if you want to classify packets based on the control | |
336 | cgroup of their process. | |
337 | ||
1da177e4 LT |
338 | config NET_EMATCH |
339 | bool "Extended Matches" | |
52ab4ac2 | 340 | select NET_CLS |
1da177e4 LT |
341 | ---help--- |
342 | Say Y here if you want to use extended matches on top of classifiers | |
343 | and select the extended matches below. | |
344 | ||
345 | Extended matches are small classification helpers not worth writing | |
52ab4ac2 | 346 | a separate classifier for. |
1da177e4 | 347 | |
52ab4ac2 | 348 | A recent version of the iproute2 package is required to use |
1da177e4 LT |
349 | extended matches. |
350 | ||
351 | config NET_EMATCH_STACK | |
352 | int "Stack size" | |
353 | depends on NET_EMATCH | |
354 | default "32" | |
355 | ---help--- | |
356 | Size of the local stack variable used while evaluating the tree of | |
357 | ematches. Limits the depth of the tree, i.e. the number of | |
b824979a | 358 | encapsulated precedences. Every level requires 4 bytes of additional |
1da177e4 LT |
359 | stack space. |
360 | ||
361 | config NET_EMATCH_CMP | |
362 | tristate "Simple packet data comparison" | |
363 | depends on NET_EMATCH | |
364 | ---help--- | |
365 | Say Y here if you want to be able to classify packets based on | |
366 | simple packet data comparisons for 8, 16, and 32bit values. | |
367 | ||
368 | To compile this code as a module, choose M here: the | |
369 | module will be called em_cmp. | |
370 | ||
371 | config NET_EMATCH_NBYTE | |
372 | tristate "Multi byte comparison" | |
373 | depends on NET_EMATCH | |
374 | ---help--- | |
375 | Say Y here if you want to be able to classify packets based on | |
376 | multiple byte comparisons mainly useful for IPv6 address comparisons. | |
377 | ||
378 | To compile this code as a module, choose M here: the | |
379 | module will be called em_nbyte. | |
380 | ||
381 | config NET_EMATCH_U32 | |
52ab4ac2 | 382 | tristate "U32 key" |
1da177e4 LT |
383 | depends on NET_EMATCH |
384 | ---help--- | |
385 | Say Y here if you want to be able to classify packets using | |
386 | the famous u32 key in combination with logic relations. | |
387 | ||
388 | To compile this code as a module, choose M here: the | |
389 | module will be called em_u32. | |
390 | ||
391 | config NET_EMATCH_META | |
392 | tristate "Metadata" | |
393 | depends on NET_EMATCH | |
394 | ---help--- | |
bb7e8c5a | 395 | Say Y here if you want to be able to classify packets based on |
1da177e4 LT |
396 | metadata such as load average, netfilter attributes, socket |
397 | attributes and routing decisions. | |
398 | ||
399 | To compile this code as a module, choose M here: the | |
400 | module will be called em_meta. | |
401 | ||
d675c989 TG |
402 | config NET_EMATCH_TEXT |
403 | tristate "Textsearch" | |
404 | depends on NET_EMATCH | |
f2d368fa | 405 | select TEXTSEARCH |
f7704347 | 406 | select TEXTSEARCH_KMP |
29cb9f9c | 407 | select TEXTSEARCH_BM |
f7704347 | 408 | select TEXTSEARCH_FSM |
d675c989 | 409 | ---help--- |
52ab4ac2 | 410 | Say Y here if you want to be able to classify packets based on |
f7704347 | 411 | textsearch comparisons. |
d675c989 TG |
412 | |
413 | To compile this code as a module, choose M here: the | |
414 | module will be called em_text. | |
415 | ||
1da177e4 | 416 | config NET_CLS_ACT |
52ab4ac2 | 417 | bool "Actions" |
1da177e4 | 418 | ---help--- |
52ab4ac2 TG |
419 | Say Y here if you want to use traffic control actions. Actions |
420 | get attached to classifiers and are invoked after a successful | |
421 | classification. They are used to overwrite the classification | |
422 | result, instantly drop or redirect packets, etc. | |
423 | ||
424 | A recent version of the iproute2 package is required to use | |
425 | extended matches. | |
1da177e4 LT |
426 | |
427 | config NET_ACT_POLICE | |
52ab4ac2 | 428 | tristate "Traffic Policing" |
1da177e4 LT |
429 | depends on NET_CLS_ACT |
430 | ---help--- | |
52ab4ac2 TG |
431 | Say Y here if you want to do traffic policing, i.e. strict |
432 | bandwidth limiting. This action replaces the existing policing | |
433 | module. | |
434 | ||
435 | To compile this code as a module, choose M here: the | |
436 | module will be called police. | |
1da177e4 LT |
437 | |
438 | config NET_ACT_GACT | |
52ab4ac2 | 439 | tristate "Generic actions" |
1da177e4 LT |
440 | depends on NET_CLS_ACT |
441 | ---help--- | |
52ab4ac2 TG |
442 | Say Y here to take generic actions such as dropping and |
443 | accepting packets. | |
444 | ||
445 | To compile this code as a module, choose M here: the | |
446 | module will be called gact. | |
1da177e4 LT |
447 | |
448 | config GACT_PROB | |
52ab4ac2 | 449 | bool "Probability support" |
1da177e4 LT |
450 | depends on NET_ACT_GACT |
451 | ---help--- | |
52ab4ac2 | 452 | Say Y here to use the generic action randomly or deterministically. |
1da177e4 LT |
453 | |
454 | config NET_ACT_MIRRED | |
52ab4ac2 | 455 | tristate "Redirecting and Mirroring" |
1da177e4 LT |
456 | depends on NET_CLS_ACT |
457 | ---help--- | |
52ab4ac2 TG |
458 | Say Y here to allow packets to be mirrored or redirected to |
459 | other devices. | |
460 | ||
461 | To compile this code as a module, choose M here: the | |
462 | module will be called mirred. | |
1da177e4 LT |
463 | |
464 | config NET_ACT_IPT | |
52ab4ac2 | 465 | tristate "IPtables targets" |
1da177e4 LT |
466 | depends on NET_CLS_ACT && NETFILTER && IP_NF_IPTABLES |
467 | ---help--- | |
3539c272 | 468 | Say Y here to be able to invoke iptables targets after successful |
52ab4ac2 TG |
469 | classification. |
470 | ||
471 | To compile this code as a module, choose M here: the | |
472 | module will be called ipt. | |
1da177e4 | 473 | |
b4219952 HX |
474 | config NET_ACT_NAT |
475 | tristate "Stateless NAT" | |
476 | depends on NET_CLS_ACT | |
b4219952 HX |
477 | ---help--- |
478 | Say Y here to do stateless NAT on IPv4 packets. You should use | |
479 | netfilter for NAT unless you know what you are doing. | |
480 | ||
481 | To compile this code as a module, choose M here: the | |
482 | module will be called nat. | |
483 | ||
1da177e4 | 484 | config NET_ACT_PEDIT |
52ab4ac2 | 485 | tristate "Packet Editing" |
1da177e4 LT |
486 | depends on NET_CLS_ACT |
487 | ---help--- | |
52ab4ac2 | 488 | Say Y here if you want to mangle the content of packets. |
1da177e4 | 489 | |
52ab4ac2 TG |
490 | To compile this code as a module, choose M here: the |
491 | module will be called pedit. | |
1da177e4 | 492 | |
db753079 | 493 | config NET_ACT_SIMP |
52ab4ac2 | 494 | tristate "Simple Example (Debug)" |
db753079 JHS |
495 | depends on NET_CLS_ACT |
496 | ---help--- | |
52ab4ac2 TG |
497 | Say Y here to add a simple action for demonstration purposes. |
498 | It is meant as an example and for debugging purposes. It will | |
499 | print a configured policy string followed by the packet count | |
500 | to the console for every packet that passes by. | |
501 | ||
502 | If unsure, say N. | |
503 | ||
504 | To compile this code as a module, choose M here: the | |
505 | module will be called simple. | |
506 | ||
ca9b0e27 AD |
507 | config NET_ACT_SKBEDIT |
508 | tristate "SKB Editing" | |
509 | depends on NET_CLS_ACT | |
510 | ---help--- | |
511 | Say Y here to change skb priority or queue_mapping settings. | |
512 | ||
513 | If unsure, say N. | |
514 | ||
515 | To compile this code as a module, choose M here: the | |
516 | module will be called skbedit. | |
517 | ||
52ab4ac2 TG |
518 | config NET_CLS_IND |
519 | bool "Incoming device classification" | |
05b8b0fa | 520 | depends on NET_CLS_U32 || NET_CLS_FW |
52ab4ac2 TG |
521 | ---help--- |
522 | Say Y here to extend the u32 and fw classifier to support | |
523 | classification based on the incoming device. This option is | |
524 | likely to disappear in favour of the metadata ematch. | |
525 | ||
05b8b0fa RZ |
526 | endif # NET_SCHED |
527 | ||
85ef3e5c RD |
528 | config NET_SCH_FIFO |
529 | bool |