1# 2# Traffic control configuration. 3# 4 5menuconfig NET_SCHED 6 bool "QoS and/or fair queueing" 7 select NET_SCH_FIFO 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 11 delay, and which ones to drop. This is the job of the queueing 12 disciplines, several different algorithms for how to do this 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 26 <https://www.kernel.org/pub/linux/utils/net/iproute2/>. That package 27 also contains some documentation; for more, check out 28 <http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2>. 29 30 This Quality of Service (QoS) support will enable you to use 31 Differentiated Services (diffserv) and Resource Reservation Protocol 32 (RSVP) on your Linux router if you also say Y to the corresponding 33 classifiers below. Documentation and software is at 34 <http://diffserv.sourceforge.net/>. 35 36 If you say Y here and to "/proc file system" below, you will be able 37 to read status information about packet schedulers from the file 38 /proc/net/psched. 39 40 The available schedulers are listed in the following questions; you 41 can say Y to as many as you like. If unsure, say N now. 42 43if NET_SCHED 44 45comment "Queueing/Scheduling" 46 47config NET_SCH_CBQ 48 tristate "Class Based Queueing (CBQ)" 49 ---help--- 50 Say Y here if you want to use the Class-Based Queueing (CBQ) packet 51 scheduling algorithm. This algorithm classifies the waiting packets 52 into a tree-like hierarchy of classes; the leaves of this tree are 53 in turn scheduled by separate algorithms. 54 55 See the top of <file:net/sched/sch_cbq.c> for more details. 56 57 CBQ is a commonly used scheduler, so if you're unsure, you should 58 say Y here. Then say Y to all the queueing algorithms below that you 59 want to use as leaf disciplines. 60 61 To compile this code as a module, choose M here: the 62 module will be called sch_cbq. 63 64config NET_SCH_HTB 65 tristate "Hierarchical Token Bucket (HTB)" 66 ---help--- 67 Say Y here if you want to use the Hierarchical Token Buckets (HTB) 68 packet scheduling algorithm. See 69 <http://luxik.cdi.cz/~devik/qos/htb/> for complete manual and 70 in-depth articles. 71 72 HTB is very similar to CBQ regarding its goals however is has 73 different properties and different algorithm. 74 75 To compile this code as a module, choose M here: the 76 module will be called sch_htb. 77 78config NET_SCH_HFSC 79 tristate "Hierarchical Fair Service Curve (HFSC)" 80 ---help--- 81 Say Y here if you want to use the Hierarchical Fair Service Curve 82 (HFSC) packet scheduling algorithm. 83 84 To compile this code as a module, choose M here: the 85 module will be called sch_hfsc. 86 87config NET_SCH_ATM 88 tristate "ATM Virtual Circuits (ATM)" 89 depends on ATM 90 ---help--- 91 Say Y here if you want to use the ATM pseudo-scheduler. This 92 provides a framework for invoking classifiers, which in turn 93 select classes of this queuing discipline. Each class maps 94 the flow(s) it is handling to a given virtual circuit. 95 96 See the top of <file:net/sched/sch_atm.c> for more details. 97 98 To compile this code as a module, choose M here: the 99 module will be called sch_atm. 100 101config NET_SCH_PRIO 102 tristate "Multi Band Priority Queueing (PRIO)" 103 ---help--- 104 Say Y here if you want to use an n-band priority queue packet 105 scheduler. 106 107 To compile this code as a module, choose M here: the 108 module will be called sch_prio. 109 110config NET_SCH_MULTIQ 111 tristate "Hardware Multiqueue-aware Multi Band Queuing (MULTIQ)" 112 ---help--- 113 Say Y here if you want to use an n-band queue packet scheduler 114 to support devices that have multiple hardware transmit queues. 115 116 To compile this code as a module, choose M here: the 117 module will be called sch_multiq. 118 119config NET_SCH_RED 120 tristate "Random Early Detection (RED)" 121 ---help--- 122 Say Y here if you want to use the Random Early Detection (RED) 123 packet scheduling algorithm. 124 125 See the top of <file:net/sched/sch_red.c> for more details. 126 127 To compile this code as a module, choose M here: the 128 module will be called sch_red. 129 130config NET_SCH_SFB 131 tristate "Stochastic Fair Blue (SFB)" 132 ---help--- 133 Say Y here if you want to use the Stochastic Fair Blue (SFB) 134 packet scheduling algorithm. 135 136 See the top of <file:net/sched/sch_sfb.c> for more details. 137 138 To compile this code as a module, choose M here: the 139 module will be called sch_sfb. 140 141config NET_SCH_SFQ 142 tristate "Stochastic Fairness Queueing (SFQ)" 143 ---help--- 144 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ) 145 packet scheduling algorithm. 146 147 See the top of <file:net/sched/sch_sfq.c> for more details. 148 149 To compile this code as a module, choose M here: the 150 module will be called sch_sfq. 151 152config NET_SCH_TEQL 153 tristate "True Link Equalizer (TEQL)" 154 ---help--- 155 Say Y here if you want to use the True Link Equalizer (TLE) packet 156 scheduling algorithm. This queueing discipline allows the combination 157 of several physical devices into one virtual device. 158 159 See the top of <file:net/sched/sch_teql.c> for more details. 160 161 To compile this code as a module, choose M here: the 162 module will be called sch_teql. 163 164config NET_SCH_TBF 165 tristate "Token Bucket Filter (TBF)" 166 ---help--- 167 Say Y here if you want to use the Token Bucket Filter (TBF) packet 168 scheduling algorithm. 169 170 See the top of <file:net/sched/sch_tbf.c> for more details. 171 172 To compile this code as a module, choose M here: the 173 module will be called sch_tbf. 174 175config NET_SCH_CBS 176 tristate "Credit Based Shaper (CBS)" 177 ---help--- 178 Say Y here if you want to use the Credit Based Shaper (CBS) packet 179 scheduling algorithm. 180 181 See the top of <file:net/sched/sch_cbs.c> for more details. 182 183 To compile this code as a module, choose M here: the 184 module will be called sch_cbs. 185 186config NET_SCH_ETF 187 tristate "Earliest TxTime First (ETF)" 188 help 189 Say Y here if you want to use the Earliest TxTime First (ETF) packet 190 scheduling algorithm. 191 192 See the top of <file:net/sched/sch_etf.c> for more details. 193 194 To compile this code as a module, choose M here: the 195 module will be called sch_etf. 196 197config NET_SCH_GRED 198 tristate "Generic Random Early Detection (GRED)" 199 ---help--- 200 Say Y here if you want to use the Generic Random Early Detection 201 (GRED) packet scheduling algorithm for some of your network devices 202 (see the top of <file:net/sched/sch_red.c> for details and 203 references about the algorithm). 204 205 To compile this code as a module, choose M here: the 206 module will be called sch_gred. 207 208config NET_SCH_DSMARK 209 tristate "Differentiated Services marker (DSMARK)" 210 ---help--- 211 Say Y if you want to schedule packets according to the 212 Differentiated Services architecture proposed in RFC 2475. 213 Technical information on this method, with pointers to associated 214 RFCs, is available at <http://www.gta.ufrj.br/diffserv/>. 215 216 To compile this code as a module, choose M here: the 217 module will be called sch_dsmark. 218 219config NET_SCH_NETEM 220 tristate "Network emulator (NETEM)" 221 ---help--- 222 Say Y if you want to emulate network delay, loss, and packet 223 re-ordering. This is often useful to simulate networks when 224 testing applications or protocols. 225 226 To compile this driver as a module, choose M here: the module 227 will be called sch_netem. 228 229 If unsure, say N. 230 231config NET_SCH_DRR 232 tristate "Deficit Round Robin scheduler (DRR)" 233 help 234 Say Y here if you want to use the Deficit Round Robin (DRR) packet 235 scheduling algorithm. 236 237 To compile this driver as a module, choose M here: the module 238 will be called sch_drr. 239 240 If unsure, say N. 241 242config NET_SCH_MQPRIO 243 tristate "Multi-queue priority scheduler (MQPRIO)" 244 help 245 Say Y here if you want to use the Multi-queue Priority scheduler. 246 This scheduler allows QOS to be offloaded on NICs that have support 247 for offloading QOS schedulers. 248 249 To compile this driver as a module, choose M here: the module will 250 be called sch_mqprio. 251 252 If unsure, say N. 253 254config NET_SCH_SKBPRIO 255 tristate "SKB priority queue scheduler (SKBPRIO)" 256 help 257 Say Y here if you want to use the SKB priority queue 258 scheduler. This schedules packets according to skb->priority, 259 which is useful for request packets in DoS mitigation systems such 260 as Gatekeeper. 261 262 To compile this driver as a module, choose M here: the module will 263 be called sch_skbprio. 264 265 If unsure, say N. 266 267config NET_SCH_CHOKE 268 tristate "CHOose and Keep responsive flow scheduler (CHOKE)" 269 help 270 Say Y here if you want to use the CHOKe packet scheduler (CHOose 271 and Keep for responsive flows, CHOose and Kill for unresponsive 272 flows). This is a variation of RED which trys to penalize flows 273 that monopolize the queue. 274 275 To compile this code as a module, choose M here: the 276 module will be called sch_choke. 277 278config NET_SCH_QFQ 279 tristate "Quick Fair Queueing scheduler (QFQ)" 280 help 281 Say Y here if you want to use the Quick Fair Queueing Scheduler (QFQ) 282 packet scheduling algorithm. 283 284 To compile this driver as a module, choose M here: the module 285 will be called sch_qfq. 286 287 If unsure, say N. 288 289config NET_SCH_CODEL 290 tristate "Controlled Delay AQM (CODEL)" 291 help 292 Say Y here if you want to use the Controlled Delay (CODEL) 293 packet scheduling algorithm. 294 295 To compile this driver as a module, choose M here: the module 296 will be called sch_codel. 297 298 If unsure, say N. 299 300config NET_SCH_FQ_CODEL 301 tristate "Fair Queue Controlled Delay AQM (FQ_CODEL)" 302 help 303 Say Y here if you want to use the FQ Controlled Delay (FQ_CODEL) 304 packet scheduling algorithm. 305 306 To compile this driver as a module, choose M here: the module 307 will be called sch_fq_codel. 308 309 If unsure, say N. 310 311config NET_SCH_CAKE 312 tristate "Common Applications Kept Enhanced (CAKE)" 313 help 314 Say Y here if you want to use the Common Applications Kept Enhanced 315 (CAKE) queue management algorithm. 316 317 To compile this driver as a module, choose M here: the module 318 will be called sch_cake. 319 320 If unsure, say N. 321 322config NET_SCH_FQ 323 tristate "Fair Queue" 324 help 325 Say Y here if you want to use the FQ packet scheduling algorithm. 326 327 FQ does flow separation, and is able to respect pacing requirements 328 set by TCP stack into sk->sk_pacing_rate (for localy generated 329 traffic) 330 331 To compile this driver as a module, choose M here: the module 332 will be called sch_fq. 333 334 If unsure, say N. 335 336config NET_SCH_HHF 337 tristate "Heavy-Hitter Filter (HHF)" 338 help 339 Say Y here if you want to use the Heavy-Hitter Filter (HHF) 340 packet scheduling algorithm. 341 342 To compile this driver as a module, choose M here: the module 343 will be called sch_hhf. 344 345config NET_SCH_PIE 346 tristate "Proportional Integral controller Enhanced (PIE) scheduler" 347 help 348 Say Y here if you want to use the Proportional Integral controller 349 Enhanced scheduler packet scheduling algorithm. 350 For more information, please see 351 http://tools.ietf.org/html/draft-pan-tsvwg-pie-00 352 353 To compile this driver as a module, choose M here: the module 354 will be called sch_pie. 355 356 If unsure, say N. 357 358config NET_SCH_INGRESS 359 tristate "Ingress/classifier-action Qdisc" 360 depends on NET_CLS_ACT 361 select NET_INGRESS 362 select NET_EGRESS 363 ---help--- 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 370 If unsure, say Y. 371 372 To compile this code as a module, choose M here: the module will be 373 called sch_ingress with alias of sch_clsact. 374 375config NET_SCH_PLUG 376 tristate "Plug network traffic until release (PLUG)" 377 ---help--- 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 393 For more information, please refer to <http://wiki.xenproject.org/wiki/Remus> 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 401menuconfig NET_SCH_DEFAULT 402 bool "Allow override default queue discipline" 403 ---help--- 404 Support for selection of default queuing discipline. 405 406 Nearly all users can safely say no here, and the default 407 of pfifo_fast will be used. Many distributions already set 408 the default value via /proc/sys/net/core/default_qdisc. 409 410 If unsure, say N. 411 412if NET_SCH_DEFAULT 413 414choice 415 prompt "Default queuing discipline" 416 default DEFAULT_PFIFO_FAST 417 help 418 Select the queueing discipline that will be used by default 419 for all network devices. 420 421 config DEFAULT_FQ 422 bool "Fair Queue" if NET_SCH_FQ 423 424 config DEFAULT_CODEL 425 bool "Controlled Delay" if NET_SCH_CODEL 426 427 config DEFAULT_FQ_CODEL 428 bool "Fair Queue Controlled Delay" if NET_SCH_FQ_CODEL 429 430 config DEFAULT_SFQ 431 bool "Stochastic Fair Queue" if NET_SCH_SFQ 432 433 config DEFAULT_PFIFO_FAST 434 bool "Priority FIFO Fast" 435endchoice 436 437config DEFAULT_NET_SCH 438 string 439 default "pfifo_fast" if DEFAULT_PFIFO_FAST 440 default "fq" if DEFAULT_FQ 441 default "fq_codel" if DEFAULT_FQ_CODEL 442 default "sfq" if DEFAULT_SFQ 443 default "pfifo_fast" 444endif 445 446comment "Classification" 447 448config NET_CLS 449 bool 450 451config NET_CLS_BASIC 452 tristate "Elementary classification (BASIC)" 453 select NET_CLS 454 ---help--- 455 Say Y here if you want to be able to classify packets using 456 only extended matches and actions. 457 458 To compile this code as a module, choose M here: the 459 module will be called cls_basic. 460 461config NET_CLS_TCINDEX 462 tristate "Traffic-Control Index (TCINDEX)" 463 select NET_CLS 464 ---help--- 465 Say Y here if you want to be able to classify packets based on 466 traffic control indices. You will want this feature if you want 467 to implement Differentiated Services together with DSMARK. 468 469 To compile this code as a module, choose M here: the 470 module will be called cls_tcindex. 471 472config NET_CLS_ROUTE4 473 tristate "Routing decision (ROUTE)" 474 depends on INET 475 select IP_ROUTE_CLASSID 476 select NET_CLS 477 ---help--- 478 If you say Y here, you will be able to classify packets 479 according to the route table entry they matched. 480 481 To compile this code as a module, choose M here: the 482 module will be called cls_route. 483 484config NET_CLS_FW 485 tristate "Netfilter mark (FW)" 486 select NET_CLS 487 ---help--- 488 If you say Y here, you will be able to classify packets 489 according to netfilter/firewall marks. 490 491 To compile this code as a module, choose M here: the 492 module will be called cls_fw. 493 494config NET_CLS_U32 495 tristate "Universal 32bit comparisons w/ hashing (U32)" 496 select NET_CLS 497 ---help--- 498 Say Y here to be able to classify packets using a universal 499 32bit pieces based comparison scheme. 500 501 To compile this code as a module, choose M here: the 502 module will be called cls_u32. 503 504config CLS_U32_PERF 505 bool "Performance counters support" 506 depends on NET_CLS_U32 507 ---help--- 508 Say Y here to make u32 gather additional statistics useful for 509 fine tuning u32 classifiers. 510 511config CLS_U32_MARK 512 bool "Netfilter marks support" 513 depends on NET_CLS_U32 514 ---help--- 515 Say Y here to be able to use netfilter marks as u32 key. 516 517config NET_CLS_RSVP 518 tristate "IPv4 Resource Reservation Protocol (RSVP)" 519 select NET_CLS 520 ---help--- 521 The Resource Reservation Protocol (RSVP) permits end systems to 522 request a minimum and maximum data flow rate for a connection; this 523 is important for real time data such as streaming sound or video. 524 525 Say Y here if you want to be able to classify outgoing packets based 526 on their RSVP requests. 527 528 To compile this code as a module, choose M here: the 529 module will be called cls_rsvp. 530 531config NET_CLS_RSVP6 532 tristate "IPv6 Resource Reservation Protocol (RSVP6)" 533 select NET_CLS 534 ---help--- 535 The Resource Reservation Protocol (RSVP) permits end systems to 536 request a minimum and maximum data flow rate for a connection; this 537 is important for real time data such as streaming sound or video. 538 539 Say Y here if you want to be able to classify outgoing packets based 540 on their RSVP requests and you are using the IPv6 protocol. 541 542 To compile this code as a module, choose M here: the 543 module will be called cls_rsvp6. 544 545config NET_CLS_FLOW 546 tristate "Flow classifier" 547 select NET_CLS 548 ---help--- 549 If you say Y here, you will be able to classify packets based on 550 a configurable combination of packet keys. This is mostly useful 551 in combination with SFQ. 552 553 To compile this code as a module, choose M here: the 554 module will be called cls_flow. 555 556config NET_CLS_CGROUP 557 tristate "Control Group Classifier" 558 select NET_CLS 559 select CGROUP_NET_CLASSID 560 depends on CGROUPS 561 ---help--- 562 Say Y here if you want to classify packets based on the control 563 cgroup of their process. 564 565 To compile this code as a module, choose M here: the 566 module will be called cls_cgroup. 567 568config NET_CLS_BPF 569 tristate "BPF-based classifier" 570 select NET_CLS 571 ---help--- 572 If you say Y here, you will be able to classify packets based on 573 programmable BPF (JIT'ed) filters as an alternative to ematches. 574 575 To compile this code as a module, choose M here: the module will 576 be called cls_bpf. 577 578config NET_CLS_FLOWER 579 tristate "Flower classifier" 580 select NET_CLS 581 ---help--- 582 If you say Y here, you will be able to classify packets based on 583 a configurable combination of packet keys and masks. 584 585 To compile this code as a module, choose M here: the module will 586 be called cls_flower. 587 588config NET_CLS_MATCHALL 589 tristate "Match-all classifier" 590 select NET_CLS 591 ---help--- 592 If you say Y here, you will be able to classify packets based on 593 nothing. Every packet will match. 594 595 To compile this code as a module, choose M here: the module will 596 be called cls_matchall. 597 598config NET_EMATCH 599 bool "Extended Matches" 600 select NET_CLS 601 ---help--- 602 Say Y here if you want to use extended matches on top of classifiers 603 and select the extended matches below. 604 605 Extended matches are small classification helpers not worth writing 606 a separate classifier for. 607 608 A recent version of the iproute2 package is required to use 609 extended matches. 610 611config NET_EMATCH_STACK 612 int "Stack size" 613 depends on NET_EMATCH 614 default "32" 615 ---help--- 616 Size of the local stack variable used while evaluating the tree of 617 ematches. Limits the depth of the tree, i.e. the number of 618 encapsulated precedences. Every level requires 4 bytes of additional 619 stack space. 620 621config NET_EMATCH_CMP 622 tristate "Simple packet data comparison" 623 depends on NET_EMATCH 624 ---help--- 625 Say Y here if you want to be able to classify packets based on 626 simple packet data comparisons for 8, 16, and 32bit values. 627 628 To compile this code as a module, choose M here: the 629 module will be called em_cmp. 630 631config NET_EMATCH_NBYTE 632 tristate "Multi byte comparison" 633 depends on NET_EMATCH 634 ---help--- 635 Say Y here if you want to be able to classify packets based on 636 multiple byte comparisons mainly useful for IPv6 address comparisons. 637 638 To compile this code as a module, choose M here: the 639 module will be called em_nbyte. 640 641config NET_EMATCH_U32 642 tristate "U32 key" 643 depends on NET_EMATCH 644 ---help--- 645 Say Y here if you want to be able to classify packets using 646 the famous u32 key in combination with logic relations. 647 648 To compile this code as a module, choose M here: the 649 module will be called em_u32. 650 651config NET_EMATCH_META 652 tristate "Metadata" 653 depends on NET_EMATCH 654 ---help--- 655 Say Y here if you want to be able to classify packets based on 656 metadata such as load average, netfilter attributes, socket 657 attributes and routing decisions. 658 659 To compile this code as a module, choose M here: the 660 module will be called em_meta. 661 662config NET_EMATCH_TEXT 663 tristate "Textsearch" 664 depends on NET_EMATCH 665 select TEXTSEARCH 666 select TEXTSEARCH_KMP 667 select TEXTSEARCH_BM 668 select TEXTSEARCH_FSM 669 ---help--- 670 Say Y here if you want to be able to classify packets based on 671 textsearch comparisons. 672 673 To compile this code as a module, choose M here: the 674 module will be called em_text. 675 676config NET_EMATCH_CANID 677 tristate "CAN Identifier" 678 depends on NET_EMATCH && (CAN=y || CAN=m) 679 ---help--- 680 Say Y here if you want to be able to classify CAN frames based 681 on CAN Identifier. 682 683 To compile this code as a module, choose M here: the 684 module will be called em_canid. 685 686config NET_EMATCH_IPSET 687 tristate "IPset" 688 depends on NET_EMATCH && IP_SET 689 ---help--- 690 Say Y here if you want to be able to classify packets based on 691 ipset membership. 692 693 To compile this code as a module, choose M here: the 694 module will be called em_ipset. 695 696config NET_EMATCH_IPT 697 tristate "IPtables Matches" 698 depends on NET_EMATCH && NETFILTER && NETFILTER_XTABLES 699 ---help--- 700 Say Y here to be able to classify packets based on iptables 701 matches. 702 Current supported match is "policy" which allows packet classification 703 based on IPsec policy that was used during decapsulation 704 705 To compile this code as a module, choose M here: the 706 module will be called em_ipt. 707 708config NET_CLS_ACT 709 bool "Actions" 710 select NET_CLS 711 ---help--- 712 Say Y here if you want to use traffic control actions. Actions 713 get attached to classifiers and are invoked after a successful 714 classification. They are used to overwrite the classification 715 result, instantly drop or redirect packets, etc. 716 717 A recent version of the iproute2 package is required to use 718 extended matches. 719 720config NET_ACT_POLICE 721 tristate "Traffic Policing" 722 depends on NET_CLS_ACT 723 ---help--- 724 Say Y here if you want to do traffic policing, i.e. strict 725 bandwidth limiting. This action replaces the existing policing 726 module. 727 728 To compile this code as a module, choose M here: the 729 module will be called act_police. 730 731config NET_ACT_GACT 732 tristate "Generic actions" 733 depends on NET_CLS_ACT 734 ---help--- 735 Say Y here to take generic actions such as dropping and 736 accepting packets. 737 738 To compile this code as a module, choose M here: the 739 module will be called act_gact. 740 741config GACT_PROB 742 bool "Probability support" 743 depends on NET_ACT_GACT 744 ---help--- 745 Say Y here to use the generic action randomly or deterministically. 746 747config NET_ACT_MIRRED 748 tristate "Redirecting and Mirroring" 749 depends on NET_CLS_ACT 750 ---help--- 751 Say Y here to allow packets to be mirrored or redirected to 752 other devices. 753 754 To compile this code as a module, choose M here: the 755 module will be called act_mirred. 756 757config NET_ACT_SAMPLE 758 tristate "Traffic Sampling" 759 depends on NET_CLS_ACT 760 select PSAMPLE 761 ---help--- 762 Say Y here to allow packet sampling tc action. The packet sample 763 action consists of statistically choosing packets and sampling 764 them using the psample module. 765 766 To compile this code as a module, choose M here: the 767 module will be called act_sample. 768 769config NET_ACT_IPT 770 tristate "IPtables targets" 771 depends on NET_CLS_ACT && NETFILTER && IP_NF_IPTABLES 772 ---help--- 773 Say Y here to be able to invoke iptables targets after successful 774 classification. 775 776 To compile this code as a module, choose M here: the 777 module will be called act_ipt. 778 779config NET_ACT_NAT 780 tristate "Stateless NAT" 781 depends on NET_CLS_ACT 782 ---help--- 783 Say Y here to do stateless NAT on IPv4 packets. You should use 784 netfilter for NAT unless you know what you are doing. 785 786 To compile this code as a module, choose M here: the 787 module will be called act_nat. 788 789config NET_ACT_PEDIT 790 tristate "Packet Editing" 791 depends on NET_CLS_ACT 792 ---help--- 793 Say Y here if you want to mangle the content of packets. 794 795 To compile this code as a module, choose M here: the 796 module will be called act_pedit. 797 798config NET_ACT_SIMP 799 tristate "Simple Example (Debug)" 800 depends on NET_CLS_ACT 801 ---help--- 802 Say Y here to add a simple action for demonstration purposes. 803 It is meant as an example and for debugging purposes. It will 804 print a configured policy string followed by the packet count 805 to the console for every packet that passes by. 806 807 If unsure, say N. 808 809 To compile this code as a module, choose M here: the 810 module will be called act_simple. 811 812config NET_ACT_SKBEDIT 813 tristate "SKB Editing" 814 depends on NET_CLS_ACT 815 ---help--- 816 Say Y here to change skb priority or queue_mapping settings. 817 818 If unsure, say N. 819 820 To compile this code as a module, choose M here: the 821 module will be called act_skbedit. 822 823config NET_ACT_CSUM 824 tristate "Checksum Updating" 825 depends on NET_CLS_ACT && INET 826 select LIBCRC32C 827 ---help--- 828 Say Y here to update some common checksum after some direct 829 packet alterations. 830 831 To compile this code as a module, choose M here: the 832 module will be called act_csum. 833 834config NET_ACT_VLAN 835 tristate "Vlan manipulation" 836 depends on NET_CLS_ACT 837 ---help--- 838 Say Y here to push or pop vlan headers. 839 840 If unsure, say N. 841 842 To compile this code as a module, choose M here: the 843 module will be called act_vlan. 844 845config NET_ACT_BPF 846 tristate "BPF based action" 847 depends on NET_CLS_ACT 848 ---help--- 849 Say Y here to execute BPF code on packets. The BPF code will decide 850 if the packet should be dropped or not. 851 852 If unsure, say N. 853 854 To compile this code as a module, choose M here: the 855 module will be called act_bpf. 856 857config NET_ACT_CONNMARK 858 tristate "Netfilter Connection Mark Retriever" 859 depends on NET_CLS_ACT && NETFILTER && IP_NF_IPTABLES 860 depends on NF_CONNTRACK && NF_CONNTRACK_MARK 861 ---help--- 862 Say Y here to allow retrieving of conn mark 863 864 If unsure, say N. 865 866 To compile this code as a module, choose M here: the 867 module will be called act_connmark. 868 869config NET_ACT_SKBMOD 870 tristate "skb data modification action" 871 depends on NET_CLS_ACT 872 ---help--- 873 Say Y here to allow modification of skb data 874 875 If unsure, say N. 876 877 To compile this code as a module, choose M here: the 878 module will be called act_skbmod. 879 880config NET_ACT_IFE 881 tristate "Inter-FE action based on IETF ForCES InterFE LFB" 882 depends on NET_CLS_ACT 883 select NET_IFE 884 ---help--- 885 Say Y here to allow for sourcing and terminating metadata 886 For details refer to netdev01 paper: 887 "Distributing Linux Traffic Control Classifier-Action Subsystem" 888 Authors: Jamal Hadi Salim and Damascene M. Joachimpillai 889 890 To compile this code as a module, choose M here: the 891 module will be called act_ife. 892 893config NET_ACT_TUNNEL_KEY 894 tristate "IP tunnel metadata manipulation" 895 depends on NET_CLS_ACT 896 ---help--- 897 Say Y here to set/release ip tunnel metadata. 898 899 If unsure, say N. 900 901 To compile this code as a module, choose M here: the 902 module will be called act_tunnel_key. 903 904config NET_IFE_SKBMARK 905 tristate "Support to encoding decoding skb mark on IFE action" 906 depends on NET_ACT_IFE 907 908config NET_IFE_SKBPRIO 909 tristate "Support to encoding decoding skb prio on IFE action" 910 depends on NET_ACT_IFE 911 912config NET_IFE_SKBTCINDEX 913 tristate "Support to encoding decoding skb tcindex on IFE action" 914 depends on NET_ACT_IFE 915 916config NET_CLS_IND 917 bool "Incoming device classification" 918 depends on NET_CLS_U32 || NET_CLS_FW 919 ---help--- 920 Say Y here to extend the u32 and fw classifier to support 921 classification based on the incoming device. This option is 922 likely to disappear in favour of the metadata ematch. 923 924endif # NET_SCHED 925 926config NET_SCH_FIFO 927 bool 928