net/sched/Kconfig

   1 #
   2 # Traffic control configuration.
   3 #
   4
   5 menuconfig 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 <ftp://ftp.tux.org/pub/net/ip-routing/>.
  26           That package also contains some documentation; for more, check out
  27           <http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2>.
  28
  29           This Quality of Service (QoS) support will enable you to use
  30           Differentiated Services (diffserv) and Resource Reservation Protocol
  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/>.
  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
  42 if NET_SCHED
  43
  44 comment "Queueing/Scheduling"
  45
  46 config NET_SCH_CBQ
  47         tristate "Class Based Queueing (CBQ)"
  48         ---help---
  49           Say Y here if you want to use the Class-Based Queueing (CBQ) packet
  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.
  53
  54           See the top of <file:net/sched/sch_cbq.c> for more details.
  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
  58           want to use as leaf disciplines.
  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
  64         tristate "Hierarchical Token Bucket (HTB)"
  65         ---help---
  66           Say Y here if you want to use the Hierarchical Token Buckets (HTB)
  67           packet scheduling algorithm. See
  68           <http://luxik.cdi.cz/~devik/qos/htb/> for complete manual and
  69           in-depth articles.
  70
  71           HTB is very similar to CBQ regarding its goals however is has
  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
  78         tristate "Hierarchical Fair Service Curve (HFSC)"
  79         ---help---
  80           Say Y here if you want to use the Hierarchical Fair Service Curve
  81           (HFSC) packet scheduling algorithm.
  82
  83           To compile this code as a module, choose M here: the
  84           module will be called sch_hfsc.
  85
  86 config NET_SCH_ATM
  87         tristate "ATM Virtual Circuits (ATM)"
  88         depends on ATM
  89         ---help---
  90           Say Y here if you want to use the ATM pseudo-scheduler.  This
  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
  95           See the top of <file:net/sched/sch_atm.c> for more details.
  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
 101         tristate "Multi Band Priority Queueing (PRIO)"
 102         ---help---
 103           Say Y here if you want to use an n-band priority queue packet
 104           scheduler.
 105
 106           To compile this code as a module, choose M here: the
 107           module will be called sch_prio.
 108
 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
 118 config NET_SCH_RED
 119         tristate "Random Early Detection (RED)"
 120         ---help---
 121           Say Y here if you want to use the Random Early Detection (RED)
 122           packet scheduling algorithm.
 123
 124           See the top of <file:net/sched/sch_red.c> for more details.
 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_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
 140 config NET_SCH_SFQ
 141         tristate "Stochastic Fairness Queueing (SFQ)"
 142         ---help---
 143           Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
 144           packet scheduling algorithm.
 145
 146           See the top of <file:net/sched/sch_sfq.c> for more details.
 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
 152         tristate "True Link Equalizer (TEQL)"
 153         ---help---
 154           Say Y here if you want to use the True Link Equalizer (TLE) packet
 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.
 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
 164         tristate "Token Bucket Filter (TBF)"
 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.
 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
 175         tristate "Generic Random Early Detection (GRED)"
 176         ---help---
 177           Say Y here if you want to use the Generic Random Early Detection
 178           (GRED) packet scheduling algorithm for some of your network devices
 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
 186         tristate "Differentiated Services marker (DSMARK)"
 187         ---help---
 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
 197         tristate "Network emulator (NETEM)"
 198         ---help---
 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
 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
 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
 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
 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
 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
 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
 275 config NET_SCH_FQ
 276         tristate "Fair Queue"
 277         help
 278           Say Y here if you want to use the FQ packet scheduling algorithm.
 279
 280           FQ does flow separation, and is able to respect pacing requirements
 281           set by TCP stack into sk->sk_pacing_rate (for localy generated
 282           traffic)
 283
 284           To compile this driver as a module, choose M here: the module
 285           will be called sch_fq.
 286
 287           If unsure, say N.
 288
 289 config NET_SCH_INGRESS
 290         tristate "Ingress Qdisc"
 291         depends on NET_CLS_ACT
 292         ---help---
 293           Say Y here if you want to use classifiers for incoming packets.
 294           If unsure, say Y.
 295
 296           To compile this code as a module, choose M here: the
 297           module will be called sch_ingress.
 298
 299 config NET_SCH_PLUG
 300         tristate "Plug network traffic until release (PLUG)"
 301         ---help---
 302
 303           This queuing discipline allows userspace to plug/unplug a network
 304           output queue, using the netlink interface.  When it receives an
 305           enqueue command it inserts a plug into the outbound queue that
 306           causes following packets to enqueue until a dequeue command arrives
 307           over netlink, causing the plug to be removed and resuming the normal
 308           packet flow.
 309
 310           This module also provides a generic "network output buffering"
 311           functionality (aka output commit), wherein upon arrival of a dequeue
 312           command, only packets up to the first plug are released for delivery.
 313           The Remus HA project uses this module to enable speculative execution
 314           of virtual machines by allowing the generated network output to be rolled
 315           back if needed.
 316
 317           For more information, please refer to http://wiki.xensource.com/xenwiki/Remus
 318
 319           Say Y here if you are using this kernel for Xen dom0 and
 320           want to protect Xen guests with Remus.
 321
 322           To compile this code as a module, choose M here: the
 323           module will be called sch_plug.
 324
 325 comment "Classification"
 326
 327 config NET_CLS
 328         boolean
 329
 330 config NET_CLS_BASIC
 331         tristate "Elementary classification (BASIC)"
 332         select NET_CLS
 333         ---help---
 334           Say Y here if you want to be able to classify packets using
 335           only extended matches and actions.
 336
 337           To compile this code as a module, choose M here: the
 338           module will be called cls_basic.
 339
 340 config NET_CLS_TCINDEX
 341         tristate "Traffic-Control Index (TCINDEX)"
 342         select NET_CLS
 343         ---help---
 344           Say Y here if you want to be able to classify packets based on
 345           traffic control indices. You will want this feature if you want
 346           to implement Differentiated Services together with DSMARK.
 347
 348           To compile this code as a module, choose M here: the
 349           module will be called cls_tcindex.
 350
 351 config NET_CLS_ROUTE4
 352         tristate "Routing decision (ROUTE)"
 353         depends on INET
 354         select IP_ROUTE_CLASSID
 355         select NET_CLS
 356         ---help---
 357           If you say Y here, you will be able to classify packets
 358           according to the route table entry they matched.
 359
 360           To compile this code as a module, choose M here: the
 361           module will be called cls_route.
 362
 363 config NET_CLS_FW
 364         tristate "Netfilter mark (FW)"
 365         select NET_CLS
 366         ---help---
 367           If you say Y here, you will be able to classify packets
 368           according to netfilter/firewall marks.
 369
 370           To compile this code as a module, choose M here: the
 371           module will be called cls_fw.
 372
 373 config NET_CLS_U32
 374         tristate "Universal 32bit comparisons w/ hashing (U32)"
 375         select NET_CLS
 376         ---help---
 377           Say Y here to be able to classify packets using a universal
 378           32bit pieces based comparison scheme.
 379
 380           To compile this code as a module, choose M here: the
 381           module will be called cls_u32.
 382
 383 config CLS_U32_PERF
 384         bool "Performance counters support"
 385         depends on NET_CLS_U32
 386         ---help---
 387           Say Y here to make u32 gather additional statistics useful for
 388           fine tuning u32 classifiers.
 389
 390 config CLS_U32_MARK
 391         bool "Netfilter marks support"
 392         depends on NET_CLS_U32
 393         ---help---
 394           Say Y here to be able to use netfilter marks as u32 key.
 395
 396 config NET_CLS_RSVP
 397         tristate "IPv4 Resource Reservation Protocol (RSVP)"
 398         select NET_CLS
 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
 405           on their RSVP requests.
 406
 407           To compile this code as a module, choose M here: the
 408           module will be called cls_rsvp.
 409
 410 config NET_CLS_RSVP6
 411         tristate "IPv6 Resource Reservation Protocol (RSVP6)"
 412         select NET_CLS
 413         ---help---
 414           The Resource Reservation Protocol (RSVP) permits end systems to
 415           request a minimum and maximum data flow rate for a connection; this
 416           is important for real time data such as streaming sound or video.
 417
 418           Say Y here if you want to be able to classify outgoing packets based
 419           on their RSVP requests and you are using the IPv6 protocol.
 420
 421           To compile this code as a module, choose M here: the
 422           module will be called cls_rsvp6.
 423
 424 config NET_CLS_FLOW
 425         tristate "Flow classifier"
 426         select NET_CLS
 427         ---help---
 428           If you say Y here, you will be able to classify packets based on
 429           a configurable combination of packet keys. This is mostly useful
 430           in combination with SFQ.
 431
 432           To compile this code as a module, choose M here: the
 433           module will be called cls_flow.
 434
 435 config NET_CLS_CGROUP
 436         tristate "Control Group Classifier"
 437         select NET_CLS
 438         select CGROUP_NET_CLASSID
 439         depends on CGROUPS
 440         ---help---
 441           Say Y here if you want to classify packets based on the control
 442           cgroup of their process.
 443
 444           To compile this code as a module, choose M here: the
 445           module will be called cls_cgroup.
 446
 447 config NET_CLS_BPF
 448         tristate "BPF-based classifier"
 449         select NET_CLS
 450         ---help---
 451           If you say Y here, you will be able to classify packets based on
 452           programmable BPF (JIT'ed) filters as an alternative to ematches.
 453
 454           To compile this code as a module, choose M here: the module will
 455           be called cls_bpf.
 456
 457 config NET_EMATCH
 458         bool "Extended Matches"
 459         select NET_CLS
 460         ---help---
 461           Say Y here if you want to use extended matches on top of classifiers
 462           and select the extended matches below.
 463
 464           Extended matches are small classification helpers not worth writing
 465           a separate classifier for.
 466
 467           A recent version of the iproute2 package is required to use
 468           extended matches.
 469
 470 config NET_EMATCH_STACK
 471         int "Stack size"
 472         depends on NET_EMATCH
 473         default "32"
 474         ---help---
 475           Size of the local stack variable used while evaluating the tree of
 476           ematches. Limits the depth of the tree, i.e. the number of
 477           encapsulated precedences. Every level requires 4 bytes of additional
 478           stack space.
 479
 480 config NET_EMATCH_CMP
 481         tristate "Simple packet data comparison"
 482         depends on NET_EMATCH
 483         ---help---
 484           Say Y here if you want to be able to classify packets based on
 485           simple packet data comparisons for 8, 16, and 32bit values.
 486
 487           To compile this code as a module, choose M here: the
 488           module will be called em_cmp.
 489
 490 config NET_EMATCH_NBYTE
 491         tristate "Multi byte comparison"
 492         depends on NET_EMATCH
 493         ---help---
 494           Say Y here if you want to be able to classify packets based on
 495           multiple byte comparisons mainly useful for IPv6 address comparisons.
 496
 497           To compile this code as a module, choose M here: the
 498           module will be called em_nbyte.
 499
 500 config NET_EMATCH_U32
 501         tristate "U32 key"
 502         depends on NET_EMATCH
 503         ---help---
 504           Say Y here if you want to be able to classify packets using
 505           the famous u32 key in combination with logic relations.
 506
 507           To compile this code as a module, choose M here: the
 508           module will be called em_u32.
 509
 510 config NET_EMATCH_META
 511         tristate "Metadata"
 512         depends on NET_EMATCH
 513         ---help---
 514           Say Y here if you want to be able to classify packets based on
 515           metadata such as load average, netfilter attributes, socket
 516           attributes and routing decisions.
 517
 518           To compile this code as a module, choose M here: the
 519           module will be called em_meta.
 520
 521 config NET_EMATCH_TEXT
 522         tristate "Textsearch"
 523         depends on NET_EMATCH
 524         select TEXTSEARCH
 525         select TEXTSEARCH_KMP
 526         select TEXTSEARCH_BM
 527         select TEXTSEARCH_FSM
 528         ---help---
 529           Say Y here if you want to be able to classify packets based on
 530           textsearch comparisons.
 531
 532           To compile this code as a module, choose M here: the
 533           module will be called em_text.
 534
 535 config NET_EMATCH_CANID
 536         tristate "CAN Identifier"
 537         depends on NET_EMATCH && (CAN=y || CAN=m)
 538         ---help---
 539           Say Y here if you want to be able to classify CAN frames based
 540           on CAN Identifier.
 541
 542           To compile this code as a module, choose M here: the
 543           module will be called em_canid.
 544
 545 config NET_EMATCH_IPSET
 546         tristate "IPset"
 547         depends on NET_EMATCH && IP_SET
 548         ---help---
 549           Say Y here if you want to be able to classify packets based on
 550           ipset membership.
 551
 552           To compile this code as a module, choose M here: the
 553           module will be called em_ipset.
 554
 555 config NET_CLS_ACT
 556         bool "Actions"
 557         ---help---
 558           Say Y here if you want to use traffic control actions. Actions
 559           get attached to classifiers and are invoked after a successful
 560           classification. They are used to overwrite the classification
 561           result, instantly drop or redirect packets, etc.
 562
 563           A recent version of the iproute2 package is required to use
 564           extended matches.
 565
 566 config NET_ACT_POLICE
 567         tristate "Traffic Policing"
 568         depends on NET_CLS_ACT
 569         ---help---
 570           Say Y here if you want to do traffic policing, i.e. strict
 571           bandwidth limiting. This action replaces the existing policing
 572           module.
 573
 574           To compile this code as a module, choose M here: the
 575           module will be called act_police.
 576
 577 config NET_ACT_GACT
 578         tristate "Generic actions"
 579         depends on NET_CLS_ACT
 580         ---help---
 581           Say Y here to take generic actions such as dropping and
 582           accepting packets.
 583
 584           To compile this code as a module, choose M here: the
 585           module will be called act_gact.
 586
 587 config GACT_PROB
 588         bool "Probability support"
 589         depends on NET_ACT_GACT
 590         ---help---
 591           Say Y here to use the generic action randomly or deterministically.
 592
 593 config NET_ACT_MIRRED
 594         tristate "Redirecting and Mirroring"
 595         depends on NET_CLS_ACT
 596         ---help---
 597           Say Y here to allow packets to be mirrored or redirected to
 598           other devices.
 599
 600           To compile this code as a module, choose M here: the
 601           module will be called act_mirred.
 602
 603 config NET_ACT_IPT
 604         tristate "IPtables targets"
 605         depends on NET_CLS_ACT && NETFILTER && IP_NF_IPTABLES
 606         ---help---
 607           Say Y here to be able to invoke iptables targets after successful
 608           classification.
 609
 610           To compile this code as a module, choose M here: the
 611           module will be called act_ipt.
 612
 613 config NET_ACT_NAT
 614         tristate "Stateless NAT"
 615         depends on NET_CLS_ACT
 616         ---help---
 617           Say Y here to do stateless NAT on IPv4 packets.  You should use
 618           netfilter for NAT unless you know what you are doing.
 619
 620           To compile this code as a module, choose M here: the
 621           module will be called act_nat.
 622
 623 config NET_ACT_PEDIT
 624         tristate "Packet Editing"
 625         depends on NET_CLS_ACT
 626         ---help---
 627           Say Y here if you want to mangle the content of packets.
 628
 629           To compile this code as a module, choose M here: the
 630           module will be called act_pedit.
 631
 632 config NET_ACT_SIMP
 633         tristate "Simple Example (Debug)"
 634         depends on NET_CLS_ACT
 635         ---help---
 636           Say Y here to add a simple action for demonstration purposes.
 637           It is meant as an example and for debugging purposes. It will
 638           print a configured policy string followed by the packet count
 639           to the console for every packet that passes by.
 640
 641           If unsure, say N.
 642
 643           To compile this code as a module, choose M here: the
 644           module will be called act_simple.
 645
 646 config NET_ACT_SKBEDIT
 647         tristate "SKB Editing"
 648         depends on NET_CLS_ACT
 649         ---help---
 650           Say Y here to change skb priority or queue_mapping settings.
 651
 652           If unsure, say N.
 653
 654           To compile this code as a module, choose M here: the
 655           module will be called act_skbedit.
 656
 657 config NET_ACT_CSUM
 658         tristate "Checksum Updating"
 659         depends on NET_CLS_ACT && INET
 660         ---help---
 661           Say Y here to update some common checksum after some direct
 662           packet alterations.
 663
 664           To compile this code as a module, choose M here: the
 665           module will be called act_csum.
 666
 667 config NET_CLS_IND
 668         bool "Incoming device classification"
 669         depends on NET_CLS_U32 || NET_CLS_FW
 670         ---help---
 671           Say Y here to extend the u32 and fw classifier to support
 672           classification based on the incoming device. This option is
 673           likely to disappear in favour of the metadata ematch.
 674
 675 endif # NET_SCHED
 676
 677 config NET_SCH_FIFO
 678         bool