# # Traffic control configuration. # config NET_SCH_CBQ tristate "CBQ packet scheduler" depends on NET_SCHED ---help--- Say Y here if you want to use the Class-Based Queueing (CBQ) packet scheduling algorithm for some of your network devices. This algorithm classifies the waiting packets into a tree-like hierarchy of classes; the leaves of this tree are in turn scheduled by separate algorithms (called "disciplines" in this context). See the top of for references about the CBQ algorithm. CBQ is a commonly used scheduler, so if you're unsure, you should say Y here. Then say Y to all the queueing algorithms below that you want to use as CBQ disciplines. Then say Y to "Packet classifier API" and say Y to all the classifiers you want to use; a classifier is a routine that allows you to sort your outgoing traffic into classes based on a certain criterion. To compile this code as a module, choose M here: the module will be called sch_cbq. config NET_SCH_HTB tristate "HTB packet scheduler" depends on NET_SCHED ---help--- Say Y here if you want to use the Hierarchical Token Buckets (HTB) packet scheduling algorithm for some of your network devices. See for complete manual and in-depth articles. HTB is very similar to the CBQ regarding its goals however is has different properties and different algorithm. To compile this code as a module, choose M here: the module will be called sch_htb. config NET_SCH_HFSC tristate "HFSC packet scheduler" depends on NET_SCHED ---help--- Say Y here if you want to use the Hierarchical Fair Service Curve (HFSC) packet scheduling algorithm for some of your network devices. To compile this code as a module, choose M here: the module will be called sch_hfsc. config NET_SCH_CSZ tristate "CSZ packet scheduler" depends on NET_SCHED ---help--- Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet scheduling algorithm for some of your network devices. At the moment, this is the only algorithm that can guarantee service for real-time applications (see the top of for details and references about the algorithm). Note: this scheduler is currently broken. To compile this code as a module, choose M here: the module will be called sch_csz. #tristate ' H-PFQ packet scheduler' CONFIG_NET_SCH_HPFQ config NET_SCH_ATM tristate "ATM pseudo-scheduler" depends on NET_SCHED && ATM ---help--- Say Y here if you want to use the ATM pseudo-scheduler. This provides a framework for invoking classifiers (aka "filters"), which in turn select classes of this queuing discipline. Each class maps the flow(s) it is handling to a given virtual circuit (see the top of ). To compile this code as a module, choose M here: the module will be called sch_atm. config NET_SCH_PRIO tristate "The simplest PRIO pseudoscheduler" depends on NET_SCHED help Say Y here if you want to use an n-band priority queue packet "scheduler" for some of your network devices or as a leaf discipline for the CBQ scheduling algorithm. If unsure, say Y. To compile this code as a module, choose M here: the module will be called sch_prio. config NET_SCH_RED tristate "RED queue" depends on NET_SCHED help Say Y here if you want to use the Random Early Detection (RED) packet scheduling algorithm for some of your network devices (see the top of for details and references about the algorithm). To compile this code as a module, choose M here: the module will be called sch_red. config NET_SCH_SFQ tristate "SFQ queue" depends on NET_SCHED ---help--- Say Y here if you want to use the Stochastic Fairness Queueing (SFQ) packet scheduling algorithm for some of your network devices or as a leaf discipline for the CBQ scheduling algorithm (see the top of for details and references about the SFQ algorithm). To compile this code as a module, choose M here: the module will be called sch_sfq. config NET_SCH_TEQL tristate "TEQL queue" depends on NET_SCHED ---help--- Say Y here if you want to use the True Link Equalizer (TLE) packet scheduling algorithm for some of your network devices or as a leaf discipline for the CBQ scheduling algorithm. This queueing discipline allows the combination of several physical devices into one virtual device. (see the top of for details). To compile this code as a module, choose M here: the module will be called sch_teql. config NET_SCH_TBF tristate "TBF queue" depends on NET_SCHED help Say Y here if you want to use the Simple Token Bucket Filter (TBF) packet scheduling algorithm for some of your network devices or as a leaf discipline for the CBQ scheduling algorithm (see the top of for a description of the TBF algorithm). To compile this code as a module, choose M here: the module will be called sch_tbf. config NET_SCH_GRED tristate "GRED queue" depends on NET_SCHED help Say Y here if you want to use the Generic Random Early Detection (RED) packet scheduling algorithm for some of your network devices (see the top of for details and references about the algorithm). To compile this code as a module, choose M here: the module will be called sch_gred. config NET_SCH_DSMARK tristate "Diffserv field marker" depends on NET_SCHED help Say Y if you want to schedule packets according to the Differentiated Services architecture proposed in RFC 2475. Technical information on this method, with pointers to associated RFCs, is available at . To compile this code as a module, choose M here: the module will be called sch_dsmark. config NET_SCH_DELAY tristate "Delay simulator" depends on NET_SCHED help Say Y if you want to delay packets by a fixed amount of time. This is often useful to simulate network delay when testing applications or protocols. To compile this driver as a module, choose M here: the module will be called sch_delay. config NET_SCH_INGRESS tristate "Ingress Qdisc" depends on NET_SCHED && NETFILTER help If you say Y here, you will be able to police incoming bandwidth and drop packets when this bandwidth exceeds your desired rate. If unsure, say Y. To compile this code as a module, choose M here: the module will be called sch_ingress. config NET_QOS bool "QoS support" depends on NET_SCHED ---help--- Say Y here if you want to include Quality Of Service scheduling features, which means that you will be able to request certain rate-of-flow limits for your network devices. This Quality of Service (QoS) support will enable you to use Differentiated Services (diffserv) and Resource Reservation Protocol (RSVP) on your Linux router if you also say Y to "Packet classifier API" and to some classifiers below. Documentation and software is at . Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about QoS support. config NET_ESTIMATOR bool "Rate estimator" depends on NET_QOS help In order for Quality of Service scheduling to work, the current rate-of-flow for a network device has to be estimated; if you say Y here, the kernel will do just that. config NET_CLS bool "Packet classifier API" depends on NET_SCHED ---help--- The CBQ scheduling algorithm requires that network packets which are scheduled to be sent out over a network device be classified according to some criterion. If you say Y here, you will get a choice of several different packet classifiers with the following questions. This will enable you to use Differentiated Services (diffserv) and Resource Reservation Protocol (RSVP) on your Linux router. Documentation and software is at . config NET_CLS_TCINDEX tristate "TC index classifier" depends on NET_CLS help If you say Y here, you will be able to classify outgoing packets according to the tc_index field of the skb. You will want this feature if you want to implement Differentiated Services using sch_dsmark. If unsure, say Y. To compile this code as a module, choose M here: the module will be called cls_tcindex. config NET_CLS_ROUTE4 tristate "Routing table based classifier" depends on NET_CLS help If you say Y here, you will be able to classify outgoing packets according to the route table entry they matched. If unsure, say Y. To compile this code as a module, choose M here: the module will be called cls_route. config NET_CLS_ROUTE bool depends on NET_CLS_ROUTE4 default y config NET_CLS_FW tristate "Firewall based classifier" depends on NET_CLS help If you say Y here, you will be able to classify outgoing packets according to firewall criteria you specified. To compile this code as a module, choose M here: the module will be called cls_fw. config NET_CLS_U32 tristate "U32 classifier" depends on NET_CLS help If you say Y here, you will be able to classify outgoing packets according to their destination address. If unsure, say Y. To compile this code as a module, choose M here: the module will be called cls_u32. config NET_CLS_RSVP tristate "Special RSVP classifier" depends on NET_CLS && NET_QOS ---help--- The Resource Reservation Protocol (RSVP) permits end systems to request a minimum and maximum data flow rate for a connection; this is important for real time data such as streaming sound or video. Say Y here if you want to be able to classify outgoing packets based on their RSVP requests. To compile this code as a module, choose M here: the module will be called cls_rsvp. config NET_CLS_RSVP6 tristate "Special RSVP classifier for IPv6" depends on NET_CLS && NET_QOS ---help--- The Resource Reservation Protocol (RSVP) permits end systems to request a minimum and maximum data flow rate for a connection; this is important for real time data such as streaming sound or video. Say Y here if you want to be able to classify outgoing packets based on their RSVP requests and you are using the new Internet Protocol IPv6 as opposed to the older and more common IPv4. To compile this code as a module, choose M here: the module will be called cls_rsvp6. config NET_CLS_POLICE bool "Traffic policing (needed for in/egress)" depends on NET_CLS && NET_QOS help Say Y to support traffic policing (bandwidth limits). Needed for ingress and egress rate limiting.