| .. | .. | 
|---|
|  | 1 | +# SPDX-License-Identifier: GPL-2.0-only | 
|---|
| 1 | 2 | # | 
|---|
| 2 | 3 | # Traffic control configuration. | 
|---|
| 3 | 4 | # | 
|---|
| .. | .. | 
|---|
| 5 | 6 | menuconfig NET_SCHED | 
|---|
| 6 | 7 | bool "QoS and/or fair queueing" | 
|---|
| 7 | 8 | select NET_SCH_FIFO | 
|---|
| 8 |  | -	---help--- | 
|---|
|  | 9 | +	help | 
|---|
| 9 | 10 | When the kernel has several packets to send out over a network | 
|---|
| 10 | 11 | device, it has to decide which ones to send first, which ones to | 
|---|
| 11 | 12 | delay, and which ones to drop. This is the job of the queueing | 
|---|
| .. | .. | 
|---|
| 46 | 47 |  | 
|---|
| 47 | 48 | config NET_SCH_CBQ | 
|---|
| 48 | 49 | tristate "Class Based Queueing (CBQ)" | 
|---|
| 49 |  | -	---help--- | 
|---|
|  | 50 | +	help | 
|---|
| 50 | 51 | Say Y here if you want to use the Class-Based Queueing (CBQ) packet | 
|---|
| 51 | 52 | scheduling algorithm. This algorithm classifies the waiting packets | 
|---|
| 52 | 53 | into a tree-like hierarchy of classes; the leaves of this tree are | 
|---|
| .. | .. | 
|---|
| 63 | 64 |  | 
|---|
| 64 | 65 | config NET_SCH_HTB | 
|---|
| 65 | 66 | tristate "Hierarchical Token Bucket (HTB)" | 
|---|
| 66 |  | -	---help--- | 
|---|
|  | 67 | +	help | 
|---|
| 67 | 68 | Say Y here if you want to use the Hierarchical Token Buckets (HTB) | 
|---|
| 68 | 69 | packet scheduling algorithm. See | 
|---|
| 69 | 70 | <http://luxik.cdi.cz/~devik/qos/htb/> for complete manual and | 
|---|
| .. | .. | 
|---|
| 77 | 78 |  | 
|---|
| 78 | 79 | config NET_SCH_HFSC | 
|---|
| 79 | 80 | tristate "Hierarchical Fair Service Curve (HFSC)" | 
|---|
| 80 |  | -	---help--- | 
|---|
|  | 81 | +	help | 
|---|
| 81 | 82 | Say Y here if you want to use the Hierarchical Fair Service Curve | 
|---|
| 82 | 83 | (HFSC) packet scheduling algorithm. | 
|---|
| 83 | 84 |  | 
|---|
| .. | .. | 
|---|
| 87 | 88 | config NET_SCH_ATM | 
|---|
| 88 | 89 | tristate "ATM Virtual Circuits (ATM)" | 
|---|
| 89 | 90 | depends on ATM | 
|---|
| 90 |  | -	---help--- | 
|---|
|  | 91 | +	help | 
|---|
| 91 | 92 | Say Y here if you want to use the ATM pseudo-scheduler.  This | 
|---|
| 92 | 93 | provides a framework for invoking classifiers, which in turn | 
|---|
| 93 | 94 | select classes of this queuing discipline.  Each class maps | 
|---|
| .. | .. | 
|---|
| 100 | 101 |  | 
|---|
| 101 | 102 | config NET_SCH_PRIO | 
|---|
| 102 | 103 | tristate "Multi Band Priority Queueing (PRIO)" | 
|---|
| 103 |  | -	---help--- | 
|---|
|  | 104 | +	help | 
|---|
| 104 | 105 | Say Y here if you want to use an n-band priority queue packet | 
|---|
| 105 | 106 | scheduler. | 
|---|
| 106 | 107 |  | 
|---|
| .. | .. | 
|---|
| 109 | 110 |  | 
|---|
| 110 | 111 | config NET_SCH_MULTIQ | 
|---|
| 111 | 112 | tristate "Hardware Multiqueue-aware Multi Band Queuing (MULTIQ)" | 
|---|
| 112 |  | -	---help--- | 
|---|
|  | 113 | +	help | 
|---|
| 113 | 114 | Say Y here if you want to use an n-band queue packet scheduler | 
|---|
| 114 | 115 | to support devices that have multiple hardware transmit queues. | 
|---|
| 115 | 116 |  | 
|---|
| .. | .. | 
|---|
| 118 | 119 |  | 
|---|
| 119 | 120 | config NET_SCH_RED | 
|---|
| 120 | 121 | tristate "Random Early Detection (RED)" | 
|---|
| 121 |  | -	---help--- | 
|---|
|  | 122 | +	help | 
|---|
| 122 | 123 | Say Y here if you want to use the Random Early Detection (RED) | 
|---|
| 123 | 124 | packet scheduling algorithm. | 
|---|
| 124 | 125 |  | 
|---|
| .. | .. | 
|---|
| 129 | 130 |  | 
|---|
| 130 | 131 | config NET_SCH_SFB | 
|---|
| 131 | 132 | tristate "Stochastic Fair Blue (SFB)" | 
|---|
| 132 |  | -	---help--- | 
|---|
|  | 133 | +	help | 
|---|
| 133 | 134 | Say Y here if you want to use the Stochastic Fair Blue (SFB) | 
|---|
| 134 | 135 | packet scheduling algorithm. | 
|---|
| 135 | 136 |  | 
|---|
| .. | .. | 
|---|
| 140 | 141 |  | 
|---|
| 141 | 142 | config NET_SCH_SFQ | 
|---|
| 142 | 143 | tristate "Stochastic Fairness Queueing (SFQ)" | 
|---|
| 143 |  | -	---help--- | 
|---|
|  | 144 | +	help | 
|---|
| 144 | 145 | Say Y here if you want to use the Stochastic Fairness Queueing (SFQ) | 
|---|
| 145 | 146 | packet scheduling algorithm. | 
|---|
| 146 | 147 |  | 
|---|
| .. | .. | 
|---|
| 151 | 152 |  | 
|---|
| 152 | 153 | config NET_SCH_TEQL | 
|---|
| 153 | 154 | tristate "True Link Equalizer (TEQL)" | 
|---|
| 154 |  | -	---help--- | 
|---|
|  | 155 | +	help | 
|---|
| 155 | 156 | Say Y here if you want to use the True Link Equalizer (TLE) packet | 
|---|
| 156 | 157 | scheduling algorithm. This queueing discipline allows the combination | 
|---|
| 157 | 158 | of several physical devices into one virtual device. | 
|---|
| .. | .. | 
|---|
| 163 | 164 |  | 
|---|
| 164 | 165 | config NET_SCH_TBF | 
|---|
| 165 | 166 | tristate "Token Bucket Filter (TBF)" | 
|---|
| 166 |  | -	---help--- | 
|---|
|  | 167 | +	help | 
|---|
| 167 | 168 | Say Y here if you want to use the Token Bucket Filter (TBF) packet | 
|---|
| 168 | 169 | scheduling algorithm. | 
|---|
| 169 | 170 |  | 
|---|
| .. | .. | 
|---|
| 174 | 175 |  | 
|---|
| 175 | 176 | config NET_SCH_CBS | 
|---|
| 176 | 177 | tristate "Credit Based Shaper (CBS)" | 
|---|
| 177 |  | -	---help--- | 
|---|
|  | 178 | +	help | 
|---|
| 178 | 179 | Say Y here if you want to use the Credit Based Shaper (CBS) packet | 
|---|
| 179 | 180 | scheduling algorithm. | 
|---|
| 180 | 181 |  | 
|---|
| .. | .. | 
|---|
| 194 | 195 | To compile this code as a module, choose M here: the | 
|---|
| 195 | 196 | module will be called sch_etf. | 
|---|
| 196 | 197 |  | 
|---|
|  | 198 | +config NET_SCH_TAPRIO | 
|---|
|  | 199 | +	tristate "Time Aware Priority (taprio) Scheduler" | 
|---|
|  | 200 | +	help | 
|---|
|  | 201 | +	  Say Y here if you want to use the Time Aware Priority (taprio) packet | 
|---|
|  | 202 | +	  scheduling algorithm. | 
|---|
|  | 203 | + | 
|---|
|  | 204 | +	  See the top of <file:net/sched/sch_taprio.c> for more details. | 
|---|
|  | 205 | + | 
|---|
|  | 206 | +	  To compile this code as a module, choose M here: the | 
|---|
|  | 207 | +	  module will be called sch_taprio. | 
|---|
|  | 208 | + | 
|---|
| 197 | 209 | config NET_SCH_GRED | 
|---|
| 198 | 210 | tristate "Generic Random Early Detection (GRED)" | 
|---|
| 199 |  | -	---help--- | 
|---|
|  | 211 | +	help | 
|---|
| 200 | 212 | Say Y here if you want to use the Generic Random Early Detection | 
|---|
| 201 | 213 | (GRED) packet scheduling algorithm for some of your network devices | 
|---|
| 202 | 214 | (see the top of <file:net/sched/sch_red.c> for details and | 
|---|
| .. | .. | 
|---|
| 207 | 219 |  | 
|---|
| 208 | 220 | config NET_SCH_DSMARK | 
|---|
| 209 | 221 | tristate "Differentiated Services marker (DSMARK)" | 
|---|
| 210 |  | -	---help--- | 
|---|
|  | 222 | +	help | 
|---|
| 211 | 223 | Say Y if you want to schedule packets according to the | 
|---|
| 212 | 224 | Differentiated Services architecture proposed in RFC 2475. | 
|---|
| 213 | 225 | Technical information on this method, with pointers to associated | 
|---|
| .. | .. | 
|---|
| 218 | 230 |  | 
|---|
| 219 | 231 | config NET_SCH_NETEM | 
|---|
| 220 | 232 | tristate "Network emulator (NETEM)" | 
|---|
| 221 |  | -	---help--- | 
|---|
|  | 233 | +	help | 
|---|
| 222 | 234 | Say Y if you want to emulate network delay, loss, and packet | 
|---|
| 223 | 235 | re-ordering. This is often useful to simulate networks when | 
|---|
| 224 | 236 | testing applications or protocols. | 
|---|
| .. | .. | 
|---|
| 312 | 324 | tristate "Common Applications Kept Enhanced (CAKE)" | 
|---|
| 313 | 325 | help | 
|---|
| 314 | 326 | Say Y here if you want to use the Common Applications Kept Enhanced | 
|---|
| 315 |  | -          (CAKE) queue management algorithm. | 
|---|
|  | 327 | +	  (CAKE) queue management algorithm. | 
|---|
| 316 | 328 |  | 
|---|
| 317 | 329 | To compile this driver as a module, choose M here: the module | 
|---|
| 318 | 330 | will be called sch_cake. | 
|---|
| .. | .. | 
|---|
| 347 | 359 | help | 
|---|
| 348 | 360 | Say Y here if you want to use the Proportional Integral controller | 
|---|
| 349 | 361 | Enhanced scheduler packet scheduling algorithm. | 
|---|
| 350 |  | -	  For more information, please see | 
|---|
| 351 |  | -	  http://tools.ietf.org/html/draft-pan-tsvwg-pie-00 | 
|---|
|  | 362 | +	  For more information, please see https://tools.ietf.org/html/rfc8033 | 
|---|
| 352 | 363 |  | 
|---|
| 353 | 364 | To compile this driver as a module, choose M here: the module | 
|---|
| 354 | 365 | will be called sch_pie. | 
|---|
|  | 366 | + | 
|---|
|  | 367 | +	  If unsure, say N. | 
|---|
|  | 368 | + | 
|---|
|  | 369 | +config NET_SCH_FQ_PIE | 
|---|
|  | 370 | +	depends on NET_SCH_PIE | 
|---|
|  | 371 | +	tristate "Flow Queue Proportional Integral controller Enhanced (FQ-PIE)" | 
|---|
|  | 372 | +	help | 
|---|
|  | 373 | +	  Say Y here if you want to use the Flow Queue Proportional Integral | 
|---|
|  | 374 | +	  controller Enhanced (FQ-PIE) packet scheduling algorithm. | 
|---|
|  | 375 | +	  For more information, please see https://tools.ietf.org/html/rfc8033 | 
|---|
|  | 376 | + | 
|---|
|  | 377 | +	  To compile this driver as a module, choose M here: the module | 
|---|
|  | 378 | +	  will be called sch_fq_pie. | 
|---|
| 355 | 379 |  | 
|---|
| 356 | 380 | If unsure, say N. | 
|---|
| 357 | 381 |  | 
|---|
| .. | .. | 
|---|
| 360 | 384 | depends on NET_CLS_ACT | 
|---|
| 361 | 385 | select NET_INGRESS | 
|---|
| 362 | 386 | select NET_EGRESS | 
|---|
| 363 |  | -	---help--- | 
|---|
|  | 387 | +	help | 
|---|
| 364 | 388 | Say Y here if you want to use classifiers for incoming and/or outgoing | 
|---|
| 365 | 389 | packets. This qdisc doesn't do anything else besides running classifiers, | 
|---|
| 366 | 390 | which can also have actions attached to them. In case of outgoing packets, | 
|---|
| .. | .. | 
|---|
| 374 | 398 |  | 
|---|
| 375 | 399 | config NET_SCH_PLUG | 
|---|
| 376 | 400 | tristate "Plug network traffic until release (PLUG)" | 
|---|
| 377 |  | -	---help--- | 
|---|
|  | 401 | +	help | 
|---|
| 378 | 402 |  | 
|---|
| 379 | 403 | This queuing discipline allows userspace to plug/unplug a network | 
|---|
| 380 | 404 | output queue, using the netlink interface.  When it receives an | 
|---|
| .. | .. | 
|---|
| 398 | 422 | To compile this code as a module, choose M here: the | 
|---|
| 399 | 423 | module will be called sch_plug. | 
|---|
| 400 | 424 |  | 
|---|
|  | 425 | +config NET_SCH_ETS | 
|---|
|  | 426 | +	tristate "Enhanced transmission selection scheduler (ETS)" | 
|---|
|  | 427 | +	help | 
|---|
|  | 428 | +          The Enhanced Transmission Selection scheduler is a classful | 
|---|
|  | 429 | +          queuing discipline that merges functionality of PRIO and DRR | 
|---|
|  | 430 | +          qdiscs in one scheduler. ETS makes it easy to configure a set of | 
|---|
|  | 431 | +          strict and bandwidth-sharing bands to implement the transmission | 
|---|
|  | 432 | +          selection described in 802.1Qaz. | 
|---|
|  | 433 | + | 
|---|
|  | 434 | +	  Say Y here if you want to use the ETS packet scheduling | 
|---|
|  | 435 | +	  algorithm. | 
|---|
|  | 436 | + | 
|---|
|  | 437 | +	  To compile this driver as a module, choose M here: the module | 
|---|
|  | 438 | +	  will be called sch_ets. | 
|---|
|  | 439 | + | 
|---|
|  | 440 | +	  If unsure, say N. | 
|---|
|  | 441 | + | 
|---|
| 401 | 442 | menuconfig NET_SCH_DEFAULT | 
|---|
| 402 | 443 | bool "Allow override default queue discipline" | 
|---|
| 403 |  | -	---help--- | 
|---|
|  | 444 | +	help | 
|---|
| 404 | 445 | Support for selection of default queuing discipline. | 
|---|
| 405 | 446 |  | 
|---|
| 406 | 447 | Nearly all users can safely say no here, and the default | 
|---|
| .. | .. | 
|---|
| 427 | 468 | config DEFAULT_FQ_CODEL | 
|---|
| 428 | 469 | bool "Fair Queue Controlled Delay" if NET_SCH_FQ_CODEL | 
|---|
| 429 | 470 |  | 
|---|
|  | 471 | +	config DEFAULT_FQ_PIE | 
|---|
|  | 472 | +		bool "Flow Queue Proportional Integral controller Enhanced" if NET_SCH_FQ_PIE | 
|---|
|  | 473 | + | 
|---|
| 430 | 474 | config DEFAULT_SFQ | 
|---|
| 431 | 475 | bool "Stochastic Fair Queue" if NET_SCH_SFQ | 
|---|
| 432 | 476 |  | 
|---|
| .. | .. | 
|---|
| 439 | 483 | default "pfifo_fast" if DEFAULT_PFIFO_FAST | 
|---|
| 440 | 484 | default "fq" if DEFAULT_FQ | 
|---|
| 441 | 485 | default "fq_codel" if DEFAULT_FQ_CODEL | 
|---|
|  | 486 | +	default "fq_pie" if DEFAULT_FQ_PIE | 
|---|
| 442 | 487 | default "sfq" if DEFAULT_SFQ | 
|---|
| 443 | 488 | default "pfifo_fast" | 
|---|
| 444 | 489 | endif | 
|---|
| .. | .. | 
|---|
| 451 | 496 | config NET_CLS_BASIC | 
|---|
| 452 | 497 | tristate "Elementary classification (BASIC)" | 
|---|
| 453 | 498 | select NET_CLS | 
|---|
| 454 |  | -	---help--- | 
|---|
|  | 499 | +	help | 
|---|
| 455 | 500 | Say Y here if you want to be able to classify packets using | 
|---|
| 456 | 501 | only extended matches and actions. | 
|---|
| 457 | 502 |  | 
|---|
| .. | .. | 
|---|
| 461 | 506 | config NET_CLS_TCINDEX | 
|---|
| 462 | 507 | tristate "Traffic-Control Index (TCINDEX)" | 
|---|
| 463 | 508 | select NET_CLS | 
|---|
| 464 |  | -	---help--- | 
|---|
|  | 509 | +	help | 
|---|
| 465 | 510 | Say Y here if you want to be able to classify packets based on | 
|---|
| 466 | 511 | traffic control indices. You will want this feature if you want | 
|---|
| 467 | 512 | to implement Differentiated Services together with DSMARK. | 
|---|
| .. | .. | 
|---|
| 474 | 519 | depends on INET | 
|---|
| 475 | 520 | select IP_ROUTE_CLASSID | 
|---|
| 476 | 521 | select NET_CLS | 
|---|
| 477 |  | -	---help--- | 
|---|
|  | 522 | +	help | 
|---|
| 478 | 523 | If you say Y here, you will be able to classify packets | 
|---|
| 479 | 524 | according to the route table entry they matched. | 
|---|
| 480 | 525 |  | 
|---|
| .. | .. | 
|---|
| 484 | 529 | config NET_CLS_FW | 
|---|
| 485 | 530 | tristate "Netfilter mark (FW)" | 
|---|
| 486 | 531 | select NET_CLS | 
|---|
| 487 |  | -	---help--- | 
|---|
|  | 532 | +	help | 
|---|
| 488 | 533 | If you say Y here, you will be able to classify packets | 
|---|
| 489 | 534 | according to netfilter/firewall marks. | 
|---|
| 490 | 535 |  | 
|---|
| .. | .. | 
|---|
| 494 | 539 | config NET_CLS_U32 | 
|---|
| 495 | 540 | tristate "Universal 32bit comparisons w/ hashing (U32)" | 
|---|
| 496 | 541 | select NET_CLS | 
|---|
| 497 |  | -	---help--- | 
|---|
|  | 542 | +	help | 
|---|
| 498 | 543 | Say Y here to be able to classify packets using a universal | 
|---|
| 499 | 544 | 32bit pieces based comparison scheme. | 
|---|
| 500 | 545 |  | 
|---|
| .. | .. | 
|---|
| 504 | 549 | config CLS_U32_PERF | 
|---|
| 505 | 550 | bool "Performance counters support" | 
|---|
| 506 | 551 | depends on NET_CLS_U32 | 
|---|
| 507 |  | -	---help--- | 
|---|
|  | 552 | +	help | 
|---|
| 508 | 553 | Say Y here to make u32 gather additional statistics useful for | 
|---|
| 509 | 554 | fine tuning u32 classifiers. | 
|---|
| 510 | 555 |  | 
|---|
| 511 | 556 | config CLS_U32_MARK | 
|---|
| 512 | 557 | bool "Netfilter marks support" | 
|---|
| 513 | 558 | depends on NET_CLS_U32 | 
|---|
| 514 |  | -	---help--- | 
|---|
|  | 559 | +	help | 
|---|
| 515 | 560 | Say Y here to be able to use netfilter marks as u32 key. | 
|---|
| 516 | 561 |  | 
|---|
| 517 | 562 | config NET_CLS_RSVP | 
|---|
| 518 | 563 | tristate "IPv4 Resource Reservation Protocol (RSVP)" | 
|---|
| 519 | 564 | select NET_CLS | 
|---|
| 520 |  | -	---help--- | 
|---|
|  | 565 | +	help | 
|---|
| 521 | 566 | The Resource Reservation Protocol (RSVP) permits end systems to | 
|---|
| 522 | 567 | request a minimum and maximum data flow rate for a connection; this | 
|---|
| 523 | 568 | is important for real time data such as streaming sound or video. | 
|---|
| .. | .. | 
|---|
| 531 | 576 | config NET_CLS_RSVP6 | 
|---|
| 532 | 577 | tristate "IPv6 Resource Reservation Protocol (RSVP6)" | 
|---|
| 533 | 578 | select NET_CLS | 
|---|
| 534 |  | -	---help--- | 
|---|
|  | 579 | +	help | 
|---|
| 535 | 580 | The Resource Reservation Protocol (RSVP) permits end systems to | 
|---|
| 536 | 581 | request a minimum and maximum data flow rate for a connection; this | 
|---|
| 537 | 582 | is important for real time data such as streaming sound or video. | 
|---|
| .. | .. | 
|---|
| 545 | 590 | config NET_CLS_FLOW | 
|---|
| 546 | 591 | tristate "Flow classifier" | 
|---|
| 547 | 592 | select NET_CLS | 
|---|
| 548 |  | -	---help--- | 
|---|
|  | 593 | +	help | 
|---|
| 549 | 594 | If you say Y here, you will be able to classify packets based on | 
|---|
| 550 | 595 | a configurable combination of packet keys. This is mostly useful | 
|---|
| 551 | 596 | in combination with SFQ. | 
|---|
| .. | .. | 
|---|
| 558 | 603 | select NET_CLS | 
|---|
| 559 | 604 | select CGROUP_NET_CLASSID | 
|---|
| 560 | 605 | depends on CGROUPS | 
|---|
| 561 |  | -	---help--- | 
|---|
|  | 606 | +	help | 
|---|
| 562 | 607 | Say Y here if you want to classify packets based on the control | 
|---|
| 563 | 608 | cgroup of their process. | 
|---|
| 564 | 609 |  | 
|---|
| .. | .. | 
|---|
| 568 | 613 | config NET_CLS_BPF | 
|---|
| 569 | 614 | tristate "BPF-based classifier" | 
|---|
| 570 | 615 | select NET_CLS | 
|---|
| 571 |  | -	---help--- | 
|---|
|  | 616 | +	help | 
|---|
| 572 | 617 | If you say Y here, you will be able to classify packets based on | 
|---|
| 573 | 618 | programmable BPF (JIT'ed) filters as an alternative to ematches. | 
|---|
| 574 | 619 |  | 
|---|
| .. | .. | 
|---|
| 578 | 623 | config NET_CLS_FLOWER | 
|---|
| 579 | 624 | tristate "Flower classifier" | 
|---|
| 580 | 625 | select NET_CLS | 
|---|
| 581 |  | -	---help--- | 
|---|
|  | 626 | +	help | 
|---|
| 582 | 627 | If you say Y here, you will be able to classify packets based on | 
|---|
| 583 | 628 | a configurable combination of packet keys and masks. | 
|---|
| 584 | 629 |  | 
|---|
| .. | .. | 
|---|
| 588 | 633 | config NET_CLS_MATCHALL | 
|---|
| 589 | 634 | tristate "Match-all classifier" | 
|---|
| 590 | 635 | select NET_CLS | 
|---|
| 591 |  | -	---help--- | 
|---|
|  | 636 | +	help | 
|---|
| 592 | 637 | If you say Y here, you will be able to classify packets based on | 
|---|
| 593 | 638 | nothing. Every packet will match. | 
|---|
| 594 | 639 |  | 
|---|
| .. | .. | 
|---|
| 598 | 643 | config NET_EMATCH | 
|---|
| 599 | 644 | bool "Extended Matches" | 
|---|
| 600 | 645 | select NET_CLS | 
|---|
| 601 |  | -	---help--- | 
|---|
|  | 646 | +	help | 
|---|
| 602 | 647 | Say Y here if you want to use extended matches on top of classifiers | 
|---|
| 603 | 648 | and select the extended matches below. | 
|---|
| 604 | 649 |  | 
|---|
| .. | .. | 
|---|
| 612 | 657 | int "Stack size" | 
|---|
| 613 | 658 | depends on NET_EMATCH | 
|---|
| 614 | 659 | default "32" | 
|---|
| 615 |  | -	---help--- | 
|---|
|  | 660 | +	help | 
|---|
| 616 | 661 | Size of the local stack variable used while evaluating the tree of | 
|---|
| 617 | 662 | ematches. Limits the depth of the tree, i.e. the number of | 
|---|
| 618 | 663 | encapsulated precedences. Every level requires 4 bytes of additional | 
|---|
| .. | .. | 
|---|
| 621 | 666 | config NET_EMATCH_CMP | 
|---|
| 622 | 667 | tristate "Simple packet data comparison" | 
|---|
| 623 | 668 | depends on NET_EMATCH | 
|---|
| 624 |  | -	---help--- | 
|---|
|  | 669 | +	help | 
|---|
| 625 | 670 | Say Y here if you want to be able to classify packets based on | 
|---|
| 626 | 671 | simple packet data comparisons for 8, 16, and 32bit values. | 
|---|
| 627 | 672 |  | 
|---|
| .. | .. | 
|---|
| 631 | 676 | config NET_EMATCH_NBYTE | 
|---|
| 632 | 677 | tristate "Multi byte comparison" | 
|---|
| 633 | 678 | depends on NET_EMATCH | 
|---|
| 634 |  | -	---help--- | 
|---|
|  | 679 | +	help | 
|---|
| 635 | 680 | Say Y here if you want to be able to classify packets based on | 
|---|
| 636 | 681 | multiple byte comparisons mainly useful for IPv6 address comparisons. | 
|---|
| 637 | 682 |  | 
|---|
| .. | .. | 
|---|
| 641 | 686 | config NET_EMATCH_U32 | 
|---|
| 642 | 687 | tristate "U32 key" | 
|---|
| 643 | 688 | depends on NET_EMATCH | 
|---|
| 644 |  | -	---help--- | 
|---|
|  | 689 | +	help | 
|---|
| 645 | 690 | Say Y here if you want to be able to classify packets using | 
|---|
| 646 | 691 | the famous u32 key in combination with logic relations. | 
|---|
| 647 | 692 |  | 
|---|
| .. | .. | 
|---|
| 651 | 696 | config NET_EMATCH_META | 
|---|
| 652 | 697 | tristate "Metadata" | 
|---|
| 653 | 698 | depends on NET_EMATCH | 
|---|
| 654 |  | -	---help--- | 
|---|
|  | 699 | +	help | 
|---|
| 655 | 700 | Say Y here if you want to be able to classify packets based on | 
|---|
| 656 | 701 | metadata such as load average, netfilter attributes, socket | 
|---|
| 657 | 702 | attributes and routing decisions. | 
|---|
| .. | .. | 
|---|
| 666 | 711 | select TEXTSEARCH_KMP | 
|---|
| 667 | 712 | select TEXTSEARCH_BM | 
|---|
| 668 | 713 | select TEXTSEARCH_FSM | 
|---|
| 669 |  | -	---help--- | 
|---|
|  | 714 | +	help | 
|---|
| 670 | 715 | Say Y here if you want to be able to classify packets based on | 
|---|
| 671 | 716 | textsearch comparisons. | 
|---|
| 672 | 717 |  | 
|---|
| .. | .. | 
|---|
| 676 | 721 | config NET_EMATCH_CANID | 
|---|
| 677 | 722 | tristate "CAN Identifier" | 
|---|
| 678 | 723 | depends on NET_EMATCH && (CAN=y || CAN=m) | 
|---|
| 679 |  | -	---help--- | 
|---|
|  | 724 | +	help | 
|---|
| 680 | 725 | Say Y here if you want to be able to classify CAN frames based | 
|---|
| 681 | 726 | on CAN Identifier. | 
|---|
| 682 | 727 |  | 
|---|
| .. | .. | 
|---|
| 686 | 731 | config NET_EMATCH_IPSET | 
|---|
| 687 | 732 | tristate "IPset" | 
|---|
| 688 | 733 | depends on NET_EMATCH && IP_SET | 
|---|
| 689 |  | -	---help--- | 
|---|
|  | 734 | +	help | 
|---|
| 690 | 735 | Say Y here if you want to be able to classify packets based on | 
|---|
| 691 | 736 | ipset membership. | 
|---|
| 692 | 737 |  | 
|---|
| .. | .. | 
|---|
| 696 | 741 | config NET_EMATCH_IPT | 
|---|
| 697 | 742 | tristate "IPtables Matches" | 
|---|
| 698 | 743 | depends on NET_EMATCH && NETFILTER && NETFILTER_XTABLES | 
|---|
| 699 |  | -	---help--- | 
|---|
|  | 744 | +	help | 
|---|
| 700 | 745 | Say Y here to be able to classify packets based on iptables | 
|---|
| 701 | 746 | matches. | 
|---|
| 702 | 747 | Current supported match is "policy" which allows packet classification | 
|---|
| .. | .. | 
|---|
| 708 | 753 | config NET_CLS_ACT | 
|---|
| 709 | 754 | bool "Actions" | 
|---|
| 710 | 755 | select NET_CLS | 
|---|
| 711 |  | -	---help--- | 
|---|
|  | 756 | +	help | 
|---|
| 712 | 757 | Say Y here if you want to use traffic control actions. Actions | 
|---|
| 713 | 758 | get attached to classifiers and are invoked after a successful | 
|---|
| 714 | 759 | classification. They are used to overwrite the classification | 
|---|
| .. | .. | 
|---|
| 719 | 764 |  | 
|---|
| 720 | 765 | config NET_ACT_POLICE | 
|---|
| 721 | 766 | tristate "Traffic Policing" | 
|---|
| 722 |  | -        depends on NET_CLS_ACT | 
|---|
| 723 |  | -        ---help--- | 
|---|
|  | 767 | +	depends on NET_CLS_ACT | 
|---|
|  | 768 | +	help | 
|---|
| 724 | 769 | Say Y here if you want to do traffic policing, i.e. strict | 
|---|
| 725 | 770 | bandwidth limiting. This action replaces the existing policing | 
|---|
| 726 | 771 | module. | 
|---|
| .. | .. | 
|---|
| 729 | 774 | module will be called act_police. | 
|---|
| 730 | 775 |  | 
|---|
| 731 | 776 | config NET_ACT_GACT | 
|---|
| 732 |  | -        tristate "Generic actions" | 
|---|
| 733 |  | -        depends on NET_CLS_ACT | 
|---|
| 734 |  | -        ---help--- | 
|---|
|  | 777 | +	tristate "Generic actions" | 
|---|
|  | 778 | +	depends on NET_CLS_ACT | 
|---|
|  | 779 | +	help | 
|---|
| 735 | 780 | Say Y here to take generic actions such as dropping and | 
|---|
| 736 | 781 | accepting packets. | 
|---|
| 737 | 782 |  | 
|---|
| .. | .. | 
|---|
| 739 | 784 | module will be called act_gact. | 
|---|
| 740 | 785 |  | 
|---|
| 741 | 786 | config GACT_PROB | 
|---|
| 742 |  | -        bool "Probability support" | 
|---|
| 743 |  | -        depends on NET_ACT_GACT | 
|---|
| 744 |  | -        ---help--- | 
|---|
|  | 787 | +	bool "Probability support" | 
|---|
|  | 788 | +	depends on NET_ACT_GACT | 
|---|
|  | 789 | +	help | 
|---|
| 745 | 790 | Say Y here to use the generic action randomly or deterministically. | 
|---|
| 746 | 791 |  | 
|---|
| 747 | 792 | config NET_ACT_MIRRED | 
|---|
| 748 |  | -        tristate "Redirecting and Mirroring" | 
|---|
| 749 |  | -        depends on NET_CLS_ACT | 
|---|
| 750 |  | -        ---help--- | 
|---|
|  | 793 | +	tristate "Redirecting and Mirroring" | 
|---|
|  | 794 | +	depends on NET_CLS_ACT | 
|---|
|  | 795 | +	help | 
|---|
| 751 | 796 | Say Y here to allow packets to be mirrored or redirected to | 
|---|
| 752 | 797 | other devices. | 
|---|
| 753 | 798 |  | 
|---|
| .. | .. | 
|---|
| 755 | 800 | module will be called act_mirred. | 
|---|
| 756 | 801 |  | 
|---|
| 757 | 802 | config NET_ACT_SAMPLE | 
|---|
| 758 |  | -        tristate "Traffic Sampling" | 
|---|
| 759 |  | -        depends on NET_CLS_ACT | 
|---|
| 760 |  | -        select PSAMPLE | 
|---|
| 761 |  | -        ---help--- | 
|---|
|  | 803 | +	tristate "Traffic Sampling" | 
|---|
|  | 804 | +	depends on NET_CLS_ACT | 
|---|
|  | 805 | +	select PSAMPLE | 
|---|
|  | 806 | +	help | 
|---|
| 762 | 807 | Say Y here to allow packet sampling tc action. The packet sample | 
|---|
| 763 | 808 | action consists of statistically choosing packets and sampling | 
|---|
| 764 | 809 | them using the psample module. | 
|---|
| .. | .. | 
|---|
| 767 | 812 | module will be called act_sample. | 
|---|
| 768 | 813 |  | 
|---|
| 769 | 814 | config NET_ACT_IPT | 
|---|
| 770 |  | -        tristate "IPtables targets" | 
|---|
| 771 |  | -        depends on NET_CLS_ACT && NETFILTER && IP_NF_IPTABLES | 
|---|
| 772 |  | -        ---help--- | 
|---|
|  | 815 | +	tristate "IPtables targets" | 
|---|
|  | 816 | +	depends on NET_CLS_ACT && NETFILTER && NETFILTER_XTABLES | 
|---|
|  | 817 | +	help | 
|---|
| 773 | 818 | Say Y here to be able to invoke iptables targets after successful | 
|---|
| 774 | 819 | classification. | 
|---|
| 775 | 820 |  | 
|---|
| .. | .. | 
|---|
| 777 | 822 | module will be called act_ipt. | 
|---|
| 778 | 823 |  | 
|---|
| 779 | 824 | config NET_ACT_NAT | 
|---|
| 780 |  | -        tristate "Stateless NAT" | 
|---|
| 781 |  | -        depends on NET_CLS_ACT | 
|---|
| 782 |  | -        ---help--- | 
|---|
|  | 825 | +	tristate "Stateless NAT" | 
|---|
|  | 826 | +	depends on NET_CLS_ACT | 
|---|
|  | 827 | +	help | 
|---|
| 783 | 828 | Say Y here to do stateless NAT on IPv4 packets.  You should use | 
|---|
| 784 | 829 | netfilter for NAT unless you know what you are doing. | 
|---|
| 785 | 830 |  | 
|---|
| .. | .. | 
|---|
| 787 | 832 | module will be called act_nat. | 
|---|
| 788 | 833 |  | 
|---|
| 789 | 834 | config NET_ACT_PEDIT | 
|---|
| 790 |  | -        tristate "Packet Editing" | 
|---|
| 791 |  | -        depends on NET_CLS_ACT | 
|---|
| 792 |  | -        ---help--- | 
|---|
|  | 835 | +	tristate "Packet Editing" | 
|---|
|  | 836 | +	depends on NET_CLS_ACT | 
|---|
|  | 837 | +	help | 
|---|
| 793 | 838 | Say Y here if you want to mangle the content of packets. | 
|---|
| 794 | 839 |  | 
|---|
| 795 | 840 | To compile this code as a module, choose M here: the | 
|---|
| 796 | 841 | module will be called act_pedit. | 
|---|
| 797 | 842 |  | 
|---|
| 798 | 843 | config NET_ACT_SIMP | 
|---|
| 799 |  | -        tristate "Simple Example (Debug)" | 
|---|
| 800 |  | -        depends on NET_CLS_ACT | 
|---|
| 801 |  | -        ---help--- | 
|---|
|  | 844 | +	tristate "Simple Example (Debug)" | 
|---|
|  | 845 | +	depends on NET_CLS_ACT | 
|---|
|  | 846 | +	help | 
|---|
| 802 | 847 | Say Y here to add a simple action for demonstration purposes. | 
|---|
| 803 | 848 | It is meant as an example and for debugging purposes. It will | 
|---|
| 804 | 849 | print a configured policy string followed by the packet count | 
|---|
| .. | .. | 
|---|
| 810 | 855 | module will be called act_simple. | 
|---|
| 811 | 856 |  | 
|---|
| 812 | 857 | config NET_ACT_SKBEDIT | 
|---|
| 813 |  | -        tristate "SKB Editing" | 
|---|
| 814 |  | -        depends on NET_CLS_ACT | 
|---|
| 815 |  | -        ---help--- | 
|---|
|  | 858 | +	tristate "SKB Editing" | 
|---|
|  | 859 | +	depends on NET_CLS_ACT | 
|---|
|  | 860 | +	help | 
|---|
| 816 | 861 | Say Y here to change skb priority or queue_mapping settings. | 
|---|
| 817 | 862 |  | 
|---|
| 818 | 863 | If unsure, say N. | 
|---|
| .. | .. | 
|---|
| 821 | 866 | module will be called act_skbedit. | 
|---|
| 822 | 867 |  | 
|---|
| 823 | 868 | config NET_ACT_CSUM | 
|---|
| 824 |  | -        tristate "Checksum Updating" | 
|---|
| 825 |  | -        depends on NET_CLS_ACT && INET | 
|---|
| 826 |  | -        select LIBCRC32C | 
|---|
| 827 |  | -        ---help--- | 
|---|
|  | 869 | +	tristate "Checksum Updating" | 
|---|
|  | 870 | +	depends on NET_CLS_ACT && INET | 
|---|
|  | 871 | +	select LIBCRC32C | 
|---|
|  | 872 | +	help | 
|---|
| 828 | 873 | Say Y here to update some common checksum after some direct | 
|---|
| 829 | 874 | packet alterations. | 
|---|
| 830 | 875 |  | 
|---|
| 831 | 876 | To compile this code as a module, choose M here: the | 
|---|
| 832 | 877 | module will be called act_csum. | 
|---|
| 833 | 878 |  | 
|---|
|  | 879 | +config NET_ACT_MPLS | 
|---|
|  | 880 | +	tristate "MPLS manipulation" | 
|---|
|  | 881 | +	depends on NET_CLS_ACT | 
|---|
|  | 882 | +	help | 
|---|
|  | 883 | +	  Say Y here to push or pop MPLS headers. | 
|---|
|  | 884 | + | 
|---|
|  | 885 | +	  If unsure, say N. | 
|---|
|  | 886 | + | 
|---|
|  | 887 | +	  To compile this code as a module, choose M here: the | 
|---|
|  | 888 | +	  module will be called act_mpls. | 
|---|
|  | 889 | + | 
|---|
| 834 | 890 | config NET_ACT_VLAN | 
|---|
| 835 |  | -        tristate "Vlan manipulation" | 
|---|
| 836 |  | -        depends on NET_CLS_ACT | 
|---|
| 837 |  | -        ---help--- | 
|---|
|  | 891 | +	tristate "Vlan manipulation" | 
|---|
|  | 892 | +	depends on NET_CLS_ACT | 
|---|
|  | 893 | +	help | 
|---|
| 838 | 894 | Say Y here to push or pop vlan headers. | 
|---|
| 839 | 895 |  | 
|---|
| 840 | 896 | If unsure, say N. | 
|---|
| .. | .. | 
|---|
| 843 | 899 | module will be called act_vlan. | 
|---|
| 844 | 900 |  | 
|---|
| 845 | 901 | config NET_ACT_BPF | 
|---|
| 846 |  | -        tristate "BPF based action" | 
|---|
| 847 |  | -        depends on NET_CLS_ACT | 
|---|
| 848 |  | -        ---help--- | 
|---|
|  | 902 | +	tristate "BPF based action" | 
|---|
|  | 903 | +	depends on NET_CLS_ACT | 
|---|
|  | 904 | +	help | 
|---|
| 849 | 905 | Say Y here to execute BPF code on packets. The BPF code will decide | 
|---|
| 850 | 906 | if the packet should be dropped or not. | 
|---|
| 851 | 907 |  | 
|---|
| .. | .. | 
|---|
| 855 | 911 | module will be called act_bpf. | 
|---|
| 856 | 912 |  | 
|---|
| 857 | 913 | config 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--- | 
|---|
|  | 914 | +	tristate "Netfilter Connection Mark Retriever" | 
|---|
|  | 915 | +	depends on NET_CLS_ACT && NETFILTER | 
|---|
|  | 916 | +	depends on NF_CONNTRACK && NF_CONNTRACK_MARK | 
|---|
|  | 917 | +	help | 
|---|
| 862 | 918 | Say Y here to allow retrieving of conn mark | 
|---|
| 863 | 919 |  | 
|---|
| 864 | 920 | If unsure, say N. | 
|---|
| .. | .. | 
|---|
| 866 | 922 | To compile this code as a module, choose M here: the | 
|---|
| 867 | 923 | module will be called act_connmark. | 
|---|
| 868 | 924 |  | 
|---|
|  | 925 | +config NET_ACT_CTINFO | 
|---|
|  | 926 | +	tristate "Netfilter Connection Mark Actions" | 
|---|
|  | 927 | +	depends on NET_CLS_ACT && NETFILTER | 
|---|
|  | 928 | +	depends on NF_CONNTRACK && NF_CONNTRACK_MARK | 
|---|
|  | 929 | +	help | 
|---|
|  | 930 | +	  Say Y here to allow transfer of a connmark stored information. | 
|---|
|  | 931 | +	  Current actions transfer connmark stored DSCP into | 
|---|
|  | 932 | +	  ipv4/v6 diffserv and/or to transfer connmark to packet | 
|---|
|  | 933 | +	  mark.  Both are useful for restoring egress based marks | 
|---|
|  | 934 | +	  back onto ingress connections for qdisc priority mapping | 
|---|
|  | 935 | +	  purposes. | 
|---|
|  | 936 | + | 
|---|
|  | 937 | +	  If unsure, say N. | 
|---|
|  | 938 | + | 
|---|
|  | 939 | +	  To compile this code as a module, choose M here: the | 
|---|
|  | 940 | +	  module will be called act_ctinfo. | 
|---|
|  | 941 | + | 
|---|
| 869 | 942 | config 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 | 
|---|
|  | 943 | +	tristate "skb data modification action" | 
|---|
|  | 944 | +	depends on NET_CLS_ACT | 
|---|
|  | 945 | +	help | 
|---|
|  | 946 | +	 Say Y here to allow modification of skb data | 
|---|
| 874 | 947 |  | 
|---|
| 875 |  | -         If unsure, say N. | 
|---|
|  | 948 | +	 If unsure, say N. | 
|---|
| 876 | 949 |  | 
|---|
| 877 |  | -         To compile this code as a module, choose M here: the | 
|---|
| 878 |  | -         module will be called act_skbmod. | 
|---|
|  | 950 | +	 To compile this code as a module, choose M here: the | 
|---|
|  | 951 | +	 module will be called act_skbmod. | 
|---|
| 879 | 952 |  | 
|---|
| 880 | 953 | config 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--- | 
|---|
|  | 954 | +	tristate "Inter-FE action based on IETF ForCES InterFE LFB" | 
|---|
|  | 955 | +	depends on NET_CLS_ACT | 
|---|
|  | 956 | +	select NET_IFE | 
|---|
|  | 957 | +	help | 
|---|
| 885 | 958 | Say Y here to allow for sourcing and terminating metadata | 
|---|
| 886 | 959 | For details refer to netdev01 paper: | 
|---|
| 887 | 960 | "Distributing Linux Traffic Control Classifier-Action Subsystem" | 
|---|
| .. | .. | 
|---|
| 891 | 964 | module will be called act_ife. | 
|---|
| 892 | 965 |  | 
|---|
| 893 | 966 | config NET_ACT_TUNNEL_KEY | 
|---|
| 894 |  | -        tristate "IP tunnel metadata manipulation" | 
|---|
| 895 |  | -        depends on NET_CLS_ACT | 
|---|
| 896 |  | -        ---help--- | 
|---|
|  | 967 | +	tristate "IP tunnel metadata manipulation" | 
|---|
|  | 968 | +	depends on NET_CLS_ACT | 
|---|
|  | 969 | +	help | 
|---|
| 897 | 970 | Say Y here to set/release ip tunnel metadata. | 
|---|
| 898 | 971 |  | 
|---|
| 899 | 972 | If unsure, say N. | 
|---|
| .. | .. | 
|---|
| 901 | 974 | To compile this code as a module, choose M here: the | 
|---|
| 902 | 975 | module will be called act_tunnel_key. | 
|---|
| 903 | 976 |  | 
|---|
|  | 977 | +config NET_ACT_CT | 
|---|
|  | 978 | +	tristate "connection tracking tc action" | 
|---|
|  | 979 | +	depends on NET_CLS_ACT && NF_CONNTRACK && (!NF_NAT || NF_NAT) && NF_FLOW_TABLE | 
|---|
|  | 980 | +	help | 
|---|
|  | 981 | +	  Say Y here to allow sending the packets to conntrack module. | 
|---|
|  | 982 | + | 
|---|
|  | 983 | +	  If unsure, say N. | 
|---|
|  | 984 | + | 
|---|
|  | 985 | +	  To compile this code as a module, choose M here: the | 
|---|
|  | 986 | +	  module will be called act_ct. | 
|---|
|  | 987 | + | 
|---|
|  | 988 | +config NET_ACT_GATE | 
|---|
|  | 989 | +	tristate "Frame gate entry list control tc action" | 
|---|
|  | 990 | +	depends on NET_CLS_ACT | 
|---|
|  | 991 | +	help | 
|---|
|  | 992 | +	  Say Y here to allow to control the ingress flow to be passed at | 
|---|
|  | 993 | +	  specific time slot and be dropped at other specific time slot by | 
|---|
|  | 994 | +	  the gate entry list. | 
|---|
|  | 995 | + | 
|---|
|  | 996 | +	  If unsure, say N. | 
|---|
|  | 997 | +	  To compile this code as a module, choose M here: the | 
|---|
|  | 998 | +	  module will be called act_gate. | 
|---|
|  | 999 | + | 
|---|
| 904 | 1000 | config NET_IFE_SKBMARK | 
|---|
| 905 |  | -        tristate "Support to encoding decoding skb mark on IFE action" | 
|---|
| 906 |  | -        depends on NET_ACT_IFE | 
|---|
|  | 1001 | +	tristate "Support to encoding decoding skb mark on IFE action" | 
|---|
|  | 1002 | +	depends on NET_ACT_IFE | 
|---|
| 907 | 1003 |  | 
|---|
| 908 | 1004 | config NET_IFE_SKBPRIO | 
|---|
| 909 |  | -        tristate "Support to encoding decoding skb prio on IFE action" | 
|---|
| 910 |  | -        depends on NET_ACT_IFE | 
|---|
|  | 1005 | +	tristate "Support to encoding decoding skb prio on IFE action" | 
|---|
|  | 1006 | +	depends on NET_ACT_IFE | 
|---|
| 911 | 1007 |  | 
|---|
| 912 | 1008 | config NET_IFE_SKBTCINDEX | 
|---|
| 913 |  | -        tristate "Support to encoding decoding skb tcindex on IFE action" | 
|---|
| 914 |  | -        depends on NET_ACT_IFE | 
|---|
|  | 1009 | +	tristate "Support to encoding decoding skb tcindex on IFE action" | 
|---|
|  | 1010 | +	depends on NET_ACT_IFE | 
|---|
| 915 | 1011 |  | 
|---|
| 916 |  | -config 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. | 
|---|
|  | 1012 | +config NET_TC_SKB_EXT | 
|---|
|  | 1013 | +	bool "TC recirculation support" | 
|---|
|  | 1014 | +	depends on NET_CLS_ACT | 
|---|
|  | 1015 | +	select SKB_EXTENSIONS | 
|---|
|  | 1016 | + | 
|---|
|  | 1017 | +	help | 
|---|
|  | 1018 | +	  Say Y here to allow tc chain misses to continue in OvS datapath in | 
|---|
|  | 1019 | +	  the correct recirc_id, and hardware chain misses to continue in | 
|---|
|  | 1020 | +	  the correct chain in tc software datapath. | 
|---|
|  | 1021 | + | 
|---|
|  | 1022 | +	  Say N here if you won't be using tc<->ovs offload or tc chains offload. | 
|---|
| 923 | 1023 |  | 
|---|
| 924 | 1024 | endif # NET_SCHED | 
|---|
| 925 | 1025 |  | 
|---|