Lines Matching full:to
10 When the kernel has several packets to send out over a network
11 device, it has to decide which ones to send first, which ones to
12 delay, and which ones to drop. This is the job of the queueing
13 disciplines, several different algorithms for how to do this
18 able to choose from among several alternative algorithms which can
19 then be attached to different network devices. This is useful for
21 need a certain minimum data flow rate, or if you need to limit the
23 This code is considered to be experimental.
25 To administer these schedulers, you'll need the user-level utilities
31 This Quality of Service (QoS) support will enable you to use
33 (RSVP) on your Linux router if you also say Y to the corresponding
37 If you say Y here and to "/proc file system" below, you will be able
38 to read status information about packet schedulers from the file
42 can say Y to as many as you like. If unsure, say N now.
51 Say Y here if you want to use the Hierarchical Token Buckets (HTB)
56 HTB is very similar to CBQ regarding its goals however is has
59 To compile this code as a module, choose M here: the
65 Say Y here if you want to use the Hierarchical Fair Service Curve
68 To compile this code as a module, choose M here: the
74 Say Y here if you want to use an n-band priority queue packet
77 To compile this code as a module, choose M here: the
83 Say Y here if you want to use an n-band queue packet scheduler
84 to support devices that have multiple hardware transmit queues.
86 To compile this code as a module, choose M here: the
92 Say Y here if you want to use the Random Early Detection (RED)
97 To compile this code as a module, choose M here: the
103 Say Y here if you want to use the Stochastic Fair Blue (SFB)
108 To compile this code as a module, choose M here: the
114 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
119 To compile this code as a module, choose M here: the
125 Say Y here if you want to use the True Link Equalizer (TLE) packet
131 To compile this code as a module, choose M here: the
137 Say Y here if you want to use the Token Bucket Filter (TBF) packet
142 To compile this code as a module, choose M here: the
148 Say Y here if you want to use the Credit Based Shaper (CBS) packet
153 To compile this code as a module, choose M here: the
159 Say Y here if you want to use the Earliest TxTime First (ETF) packet
164 To compile this code as a module, choose M here: the
176 Say Y here if you want to use the Time Aware Priority (taprio) packet
181 To compile this code as a module, choose M here: the
187 Say Y here if you want to use the Generic Random Early Detection
192 To compile this code as a module, choose M here: the
198 Say Y if you want to emulate network delay, loss, and packet
199 re-ordering. This is often useful to simulate networks when
202 To compile this driver as a module, choose M here: the module
210 Say Y here if you want to use the Deficit Round Robin (DRR) packet
213 To compile this driver as a module, choose M here: the module
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
226 To compile this driver as a module, choose M here: the module will
234 Say Y here if you want to use the SKB priority queue
235 scheduler. This schedules packets according to skb->priority,
239 To compile this driver as a module, choose M here: the module will
247 Say Y here if you want to use the CHOKe packet scheduler (CHOose
249 flows). This is a variation of RED which tries to penalize flows
252 To compile this code as a module, choose M here: the
258 Say Y here if you want to use the Quick Fair Queueing Scheduler (QFQ)
261 To compile this driver as a module, choose M here: the module
269 Say Y here if you want to use the Controlled Delay (CODEL)
272 To compile this driver as a module, choose M here: the module
280 Say Y here if you want to use the FQ Controlled Delay (FQ_CODEL)
283 To compile this driver as a module, choose M here: the module
291 Say Y here if you want to use the Common Applications Kept Enhanced
294 To compile this driver as a module, choose M here: the module
302 Say Y here if you want to use the FQ packet scheduling algorithm.
304 FQ does flow separation, and is able to respect pacing requirements
308 To compile this driver as a module, choose M here: the module
316 Say Y here if you want to use the Heavy-Hitter Filter (HHF)
319 To compile this driver as a module, choose M here: the module
325 Say Y here if you want to use the Proportional Integral controller
329 To compile this driver as a module, choose M here: the module
338 Say Y here if you want to use the Flow Queue Proportional Integral
342 To compile this driver as a module, choose M here: the module
352 Say Y here if you want to use classifiers for incoming and/or outgoing
354 which can also have actions attached to them. In case of outgoing packets,
356 before real enqueuing to an egress qdisc happens.
360 To compile this code as a module, choose M here: the module will be
367 This queuing discipline allows userspace to plug/unplug a network
370 causes following packets to enqueue until a dequeue command arrives
371 over netlink, causing the plug to be removed and resuming the normal
376 command, only packets up to the first plug are released for delivery.
377 The Remus HA project uses this module to enable speculative execution
378 of virtual machines by allowing the generated network output to be rolled
381 For more information, please refer to <http://wiki.xenproject.org/wiki/Remus>
384 want to protect Xen guests with Remus.
386 To compile this code as a module, choose M here: the
394 qdiscs in one scheduler. ETS makes it easy to configure a set of
395 strict and bandwidth-sharing bands to implement the transmission
398 Say Y here if you want to use the ETS packet scheduling
401 To compile this driver as a module, choose M here: the module
414 Say Y here if you want to use BPF-based Qdisc.
476 Say Y here if you want to be able to classify packets using
479 To compile this code as a module, choose M here: the
488 If you say Y here, you will be able to classify packets
489 according to the route table entry they matched.
491 To compile this code as a module, choose M here: the
498 If you say Y here, you will be able to classify packets
499 according to netfilter/firewall marks.
501 To compile this code as a module, choose M here: the
508 Say Y here to be able to classify packets using a universal
511 To compile this code as a module, choose M here: the
518 Say Y here to make u32 gather additional statistics useful for
525 Say Y here to be able to use netfilter marks as u32 key.
531 If you say Y here, you will be able to classify packets based on
535 To compile this code as a module, choose M here: the
544 Say Y here if you want to classify packets based on the control
547 To compile this code as a module, choose M here: the
554 If you say Y here, you will be able to classify packets based on
555 programmable BPF (JIT'ed) filters as an alternative to ematches.
557 To compile this code as a module, choose M here: the module will
564 If you say Y here, you will be able to classify packets based on
567 To compile this code as a module, choose M here: the module will
574 If you say Y here, you will be able to classify packets based on
577 To compile this code as a module, choose M here: the module will
584 Say Y here if you want to use extended matches on top of classifiers
590 A recent version of the iproute2 package is required to use
607 Say Y here if you want to be able to classify packets based on
610 To compile this code as a module, choose M here: the
617 Say Y here if you want to be able to classify packets based on
620 To compile this code as a module, choose M here: the
627 Say Y here if you want to be able to classify packets using
630 To compile this code as a module, choose M here: the
637 Say Y here if you want to be able to classify packets based on
641 To compile this code as a module, choose M here: the
652 Say Y here if you want to be able to classify packets based on
655 To compile this code as a module, choose M here: the
662 Say Y here if you want to be able to classify CAN frames based
665 To compile this code as a module, choose M here: the
672 Say Y here if you want to be able to classify packets based on
675 To compile this code as a module, choose M here: the
682 Say Y here to be able to classify packets based on iptables
687 To compile this code as a module, choose M here: the
695 Say Y here if you want to use traffic control actions. Actions
696 get attached to classifiers and are invoked after a successful
697 classification. They are used to overwrite the classification
700 A recent version of the iproute2 package is required to use
707 Say Y here if you want to do traffic policing, i.e. strict
711 To compile this code as a module, choose M here: the
718 Say Y here to take generic actions such as dropping and
721 To compile this code as a module, choose M here: the
728 Say Y here to use the generic action randomly or deterministically.
734 Say Y here to allow packets to be mirrored or redirected to
737 To compile this code as a module, choose M here: the
745 Say Y here to allow packet sampling tc action. The packet sample
749 To compile this code as a module, choose M here: the
756 Say Y here to do stateless NAT on IPv4 packets. You should use
759 To compile this code as a module, choose M here: the
766 Say Y here if you want to mangle the content of packets.
768 To compile this code as a module, choose M here: the
775 Say Y here to add a simple action for demonstration purposes.
778 to the console for every packet that passes by.
782 To compile this code as a module, choose M here: the
789 Say Y here to change skb priority or queue_mapping settings.
793 To compile this code as a module, choose M here: the
801 Say Y here to update some common checksum after some direct
804 To compile this code as a module, choose M here: the
811 Say Y here to push or pop MPLS headers.
815 To compile this code as a module, choose M here: the
822 Say Y here to push or pop vlan headers.
826 To compile this code as a module, choose M here: the
833 Say Y here to execute BPF code on packets. The BPF code will decide
838 To compile this code as a module, choose M here: the
846 Say Y here to allow retrieving of conn mark
850 To compile this code as a module, choose M here: the
858 Say Y here to allow transfer of a connmark stored information.
860 ipv4/v6 diffserv and/or to transfer connmark to packet
867 To compile this code as a module, choose M here: the
874 Say Y here to allow modification of skb data
878 To compile this code as a module, choose M here: the
886 Say Y here to allow for sourcing and terminating metadata
887 For details refer to netdev01 paper:
891 To compile this code as a module, choose M here: the
898 Say Y here to set/release ip tunnel metadata.
902 To compile this code as a module, choose M here: the
911 Say Y here to allow sending the packets to conntrack module.
915 To compile this code as a module, choose M here: the
922 Say Y here to allow to control the ingress flow to be passed at
927 To compile this code as a module, choose M here: the
931 tristate "Support to encoding decoding skb mark on IFE action"
935 tristate "Support to encoding decoding skb prio on IFE action"
939 tristate "Support to encoding decoding skb tcindex on IFE action"
948 Say Y here to allow tc chain misses to continue in OvS datapath in
949 the correct recirc_id, and hardware chain misses to continue in