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 Class-Based Queueing (CBQ) packet
59 say Y here. Then say Y to all the queueing algorithms below that you
60 want to use as leaf disciplines.
62 To compile this code as a module, choose M here: the
68 Say Y here if you want to use the Hierarchical Token Buckets (HTB)
73 HTB is very similar to CBQ regarding its goals however is has
76 To compile this code as a module, choose M here: the
82 Say Y here if you want to use the Hierarchical Fair Service Curve
85 To compile this code as a module, choose M here: the
92 Say Y here if you want to use the ATM pseudo-scheduler. This
95 the flow(s) it is handling to a given virtual circuit.
99 To compile this code as a module, choose M here: the
105 Say Y here if you want to use an n-band priority queue packet
108 To compile this code as a module, choose M here: the
114 Say Y here if you want to use an n-band queue packet scheduler
115 to support devices that have multiple hardware transmit queues.
117 To compile this code as a module, choose M here: the
123 Say Y here if you want to use the Random Early Detection (RED)
128 To compile this code as a module, choose M here: the
134 Say Y here if you want to use the Stochastic Fair Blue (SFB)
139 To compile this code as a module, choose M here: the
145 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
150 To compile this code as a module, choose M here: the
156 Say Y here if you want to use the True Link Equalizer (TLE) packet
162 To compile this code as a module, choose M here: the
168 Say Y here if you want to use the Token Bucket Filter (TBF) packet
173 To compile this code as a module, choose M here: the
179 Say Y here if you want to use the Credit Based Shaper (CBS) packet
184 To compile this code as a module, choose M here: the
190 Say Y here if you want to use the Earliest TxTime First (ETF) packet
195 To compile this code as a module, choose M here: the
201 Say Y here if you want to use the Time Aware Priority (taprio) packet
206 To compile this code as a module, choose M here: the
212 Say Y here if you want to use the Generic Random Early Detection
217 To compile this code as a module, choose M here: the
223 Say Y if you want to schedule packets according to the
225 Technical information on this method, with pointers to associated
228 To compile this code as a module, choose M here: the
234 Say Y if you want to emulate network delay, loss, and packet
235 re-ordering. This is often useful to simulate networks when
238 To compile this driver as a module, choose M here: the module
246 Say Y here if you want to use the Deficit Round Robin (DRR) packet
249 To compile this driver as a module, choose M here: the module
257 Say Y here if you want to use the Multi-queue Priority scheduler.
258 This scheduler allows QOS to be offloaded on NICs that have support
261 To compile this driver as a module, choose M here: the module will
269 Say Y here if you want to use the SKB priority queue
270 scheduler. This schedules packets according to skb->priority,
274 To compile this driver as a module, choose M here: the module will
282 Say Y here if you want to use the CHOKe packet scheduler (CHOose
284 flows). This is a variation of RED which trys to penalize flows
287 To compile this code as a module, choose M here: the
293 Say Y here if you want to use the Quick Fair Queueing Scheduler (QFQ)
296 To compile this driver as a module, choose M here: the module
304 Say Y here if you want to use the Controlled Delay (CODEL)
307 To compile this driver as a module, choose M here: the module
315 Say Y here if you want to use the FQ Controlled Delay (FQ_CODEL)
318 To compile this driver as a module, choose M here: the module
326 Say Y here if you want to use the Common Applications Kept Enhanced
329 To compile this driver as a module, choose M here: the module
337 Say Y here if you want to use the FQ packet scheduling algorithm.
339 FQ does flow separation, and is able to respect pacing requirements
343 To compile this driver as a module, choose M here: the module
351 Say Y here if you want to use the Heavy-Hitter Filter (HHF)
354 To compile this driver as a module, choose M here: the module
360 Say Y here if you want to use the Proportional Integral controller
364 To compile this driver as a module, choose M here: the module
375 Say Y here if you want to use classifiers for incoming and/or outgoing
377 which can also have actions attached to them. In case of outgoing packets,
379 before real enqueuing to an egress qdisc happens.
383 To compile this code as a module, choose M here: the module will be
390 This queuing discipline allows userspace to plug/unplug a network
393 causes following packets to enqueue until a dequeue command arrives
394 over netlink, causing the plug to be removed and resuming the normal
399 command, only packets up to the first plug are released for delivery.
400 The Remus HA project uses this module to enable speculative execution
401 of virtual machines by allowing the generated network output to be rolled
404 For more information, please refer to <http://wiki.xenproject.org/wiki/Remus>
407 want to protect Xen guests with Remus.
409 To compile this code as a module, choose M here: the
466 Say Y here if you want to be able to classify packets using
469 To compile this code as a module, choose M here: the
476 Say Y here if you want to be able to classify packets based on
478 to implement Differentiated Services together with DSMARK.
480 To compile this code as a module, choose M here: the
489 If you say Y here, you will be able to classify packets
490 according to the route table entry they matched.
492 To compile this code as a module, choose M here: the
499 If you say Y here, you will be able to classify packets
500 according to netfilter/firewall marks.
502 To compile this code as a module, choose M here: the
509 Say Y here to be able to classify packets using a universal
512 To compile this code as a module, choose M here: the
519 Say Y here to make u32 gather additional statistics useful for
526 Say Y here to be able to use netfilter marks as u32 key.
532 The Resource Reservation Protocol (RSVP) permits end systems to
536 Say Y here if you want to be able to classify outgoing packets based
539 To compile this code as a module, choose M here: the
546 The Resource Reservation Protocol (RSVP) permits end systems to
550 Say Y here if you want to be able to classify outgoing packets based
553 To compile this code as a module, choose M here: the
560 If you say Y here, you will be able to classify packets based on
564 To compile this code as a module, choose M here: the
573 Say Y here if you want to classify packets based on the control
576 To compile this code as a module, choose M here: the
583 If you say Y here, you will be able to classify packets based on
584 programmable BPF (JIT'ed) filters as an alternative to ematches.
586 To compile this code as a module, choose M here: the module will
593 If you say Y here, you will be able to classify packets based on
596 To compile this code as a module, choose M here: the module will
603 If you say Y here, you will be able to classify packets based on
606 To compile this code as a module, choose M here: the module will
613 Say Y here if you want to use extended matches on top of classifiers
619 A recent version of the iproute2 package is required to use
636 Say Y here if you want to be able to classify packets based on
639 To compile this code as a module, choose M here: the
646 Say Y here if you want to be able to classify packets based on
649 To compile this code as a module, choose M here: the
656 Say Y here if you want to be able to classify packets using
659 To compile this code as a module, choose M here: the
666 Say Y here if you want to be able to classify packets based on
670 To compile this code as a module, choose M here: the
681 Say Y here if you want to be able to classify packets based on
684 To compile this code as a module, choose M here: the
691 Say Y here if you want to be able to classify CAN frames based
694 To compile this code as a module, choose M here: the
701 Say Y here if you want to be able to classify packets based on
704 To compile this code as a module, choose M here: the
711 Say Y here to be able to classify packets based on iptables
716 To compile this code as a module, choose M here: the
723 Say Y here if you want to use traffic control actions. Actions
724 get attached to classifiers and are invoked after a successful
725 classification. They are used to overwrite the classification
728 A recent version of the iproute2 package is required to use
735 Say Y here if you want to do traffic policing, i.e. strict
739 To compile this code as a module, choose M here: the
746 Say Y here to take generic actions such as dropping and
749 To compile this code as a module, choose M here: the
756 Say Y here to use the generic action randomly or deterministically.
762 Say Y here to allow packets to be mirrored or redirected to
765 To compile this code as a module, choose M here: the
773 Say Y here to allow packet sampling tc action. The packet sample
777 To compile this code as a module, choose M here: the
784 Say Y here to be able to invoke iptables targets after successful
787 To compile this code as a module, choose M here: the
794 Say Y here to do stateless NAT on IPv4 packets. You should use
797 To compile this code as a module, choose M here: the
804 Say Y here if you want to mangle the content of packets.
806 To compile this code as a module, choose M here: the
813 Say Y here to add a simple action for demonstration purposes.
816 to the console for every packet that passes by.
820 To compile this code as a module, choose M here: the
827 Say Y here to change skb priority or queue_mapping settings.
831 To compile this code as a module, choose M here: the
839 Say Y here to update some common checksum after some direct
842 To compile this code as a module, choose M here: the
849 Say Y here to push or pop MPLS headers.
853 To compile this code as a module, choose M here: the
860 Say Y here to push or pop vlan headers.
864 To compile this code as a module, choose M here: the
871 Say Y here to execute BPF code on packets. The BPF code will decide
876 To compile this code as a module, choose M here: the
884 Say Y here to allow retrieving of conn mark
888 To compile this code as a module, choose M here: the
896 Say Y here to allow transfer of a connmark stored information.
898 ipv4/v6 diffserv and/or to transfer connmark to packet
905 To compile this code as a module, choose M here: the
912 Say Y here to allow modification of skb data
916 To compile this code as a module, choose M here: the
924 Say Y here to allow for sourcing and terminating metadata
925 For details refer to netdev01 paper:
929 To compile this code as a module, choose M here: the
936 Say Y here to set/release ip tunnel metadata.
940 To compile this code as a module, choose M here: the
947 Say Y here to allow sending the packets to conntrack module.
951 To compile this code as a module, choose M here: the
955 tristate "Support to encoding decoding skb mark on IFE action"
959 tristate "Support to encoding decoding skb prio on IFE action"
963 tristate "Support to encoding decoding skb tcindex on IFE action"
972 Say Y here to allow tc chain misses to continue in OvS datapath in
973 the correct recirc_id, and hardware chain misses to continue in