Kconfig - OpenGrok cross reference for /openbmc/linux/net/sched/Kconfig

1 # SPDX-License-Identifier: GPL-2.0-only
16 	  If you say N here, you will get the standard packet scheduler, which
25 	  To administer these schedulers, you'll need the user-level utilities
38 	  to read status information about packet schedulers from the file
52 	  packet scheduling algorithm. See
54 	  in-depth articles.
66 	  (HFSC) packet scheduling algorithm.
74 	  Say Y here if you want to use an n-band priority queue packet
81 	tristate "Hardware Multiqueue-aware Multi Band Queuing (MULTIQ)"
83 	  Say Y here if you want to use an n-band queue packet scheduler
93 	  packet scheduling algorithm.
104 	  packet scheduling algorithm.
115 	  packet scheduling algorithm.
125 	  Say Y here if you want to use the True Link Equalizer (TLE) packet
137 	  Say Y here if you want to use the Token Bucket Filter (TBF) packet
146 	tristate "Credit Based Shaper (CBS)"
148 	  Say Y here if you want to use the Credit Based Shaper (CBS) packet
159 	  Say Y here if you want to use the Earliest TxTime First (ETF) packet
176 	  Say Y here if you want to use the Time Aware Priority (taprio) packet
188 	  (GRED) packet scheduling algorithm for some of your network devices
198 	  Say Y if you want to emulate network delay, loss, and packet
199 	  re-ordering. This is often useful to simulate networks when
210 	  Say Y here if you want to use the Deficit Round Robin (DRR) packet
219 	tristate "Multi-queue priority scheduler (MQPRIO)"
222 	  Say Y here if you want to use the Multi-queue Priority scheduler.
235 	  scheduler. This schedules packets according to skb->priority,
247 	  Say Y here if you want to use the CHOKe packet scheduler (CHOose
259 	  packet scheduling algorithm.
270 	  packet scheduling algorithm.
281 	  packet scheduling algorithm.
302 	  Say Y here if you want to use the FQ packet scheduling algorithm.
305 	  set by TCP stack into sk->sk_pacing_rate (for locally generated
314 	tristate "Heavy-Hitter Filter (HHF)"
316 	  Say Y here if you want to use the Heavy-Hitter Filter (HHF)
317 	  packet scheduling algorithm.
326 	  Enhanced scheduler packet scheduling algorithm.
336 	tristate "Flow Queue Proportional Integral controller Enhanced (FQ-PIE)"
339 	  controller Enhanced (FQ-PIE) packet scheduling algorithm.
348 	tristate "Ingress/classifier-action Qdisc"
372 	  packet flow.
395           strict and bandwidth-sharing bands to implement the transmission
398 	  Say Y here if you want to use the ETS packet scheduling
497 	  32bit pieces based comparison scheme.
519 	  If you say Y here, you will be able to classify packets based on
520 	  a configurable combination of packet keys. This is mostly useful
532 	  Say Y here if you want to classify packets based on the control
539 	tristate "BPF-based classifier"
542 	  If you say Y here, you will be able to classify packets based on
552 	  If you say Y here, you will be able to classify packets based on
553 	  a configurable combination of packet keys and masks.
559 	tristate "Match-all classifier"
562 	  If you say Y here, you will be able to classify packets based on
563 	  nothing. Every packet will match.
592 	tristate "Simple packet data comparison"
595 	  Say Y here if you want to be able to classify packets based on
596 	  simple packet data comparisons for 8, 16, and 32bit values.
605 	  Say Y here if you want to be able to classify packets based on
625 	  Say Y here if you want to be able to classify packets based on
640 	  Say Y here if you want to be able to classify packets based on
650 	  Say Y here if you want to be able to classify CAN frames based
660 	  Say Y here if you want to be able to classify packets based on
670 	  Say Y here to be able to classify packets based on iptables
672 	  Current supported match is "policy" which allows packet classification
673 	  based on IPsec policy that was used during decapsulation
733 	  Say Y here to allow packet sampling tc action. The packet sample
761 	tristate "Packet Editing"
775 	  print a configured policy string followed by the packet count
776 	  to the console for every packet that passes by.
800 	  packet alterations.
828 	tristate "BPF based action"
832 	  if the packet should be dropped or not.
858 	  ipv4/v6 diffserv and/or to transfer connmark to packet
859 	  mark.  Both are useful for restoring egress based marks
880 	tristate "Inter-FE action based on IETF ForCES InterFE LFB"
886 	  "Distributing Linux Traffic Control Classifier-Action Subsystem"
950 	  Say N here if you won't be using tc<->ovs offload or tc chains offload.