Navigation: Linux Kernel Driver DataBase - web LKDDB: Main index - N index

CONFIG_NET_SCHED: QoS and/or fair queueing

General informations

The Linux kernel configuration item CONFIG_NET_SCHED has multiple definitions:

QoS and/or fair queueing found in net/sched/Kconfig

The configuration item CONFIG_NET_SCHED:

Help text

When the kernel has several packets to send out over a network device, it has to decide which ones to send first, which ones to delay, and which ones to drop. This is the job of the queueing disciplines, several different algorithms for how to do this "fairly" have been proposed.

If you say N here, you will get the standard packet scheduler, which is a FIFO (first come, first served). If you say Y here, you will be able to choose from among several alternative algorithms which can then be attached to different network devices. This is useful for example if some of your network devices are real time devices that need a certain minimum data flow rate, or if you need to limit the maximum data flow rate for traffic which matches specified criteria. This code is considered to be experimental.

To administer these schedulers, you'll need the user-level utilities from the package iproute2+tc at https://www.kernel.org/pub/linux/utils/net/iproute2/. That package also contains some documentation; for more, check out http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2.

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 the corresponding classifiers below. Documentation and software is at http://diffserv.sourceforge.net/.

If you say Y here and to "/proc file system" below, you will be able to read status information about packet schedulers from the file /proc/net/psched.

The available schedulers are listed in the following questions; you can say Y to as many as you like. If unsure, say N now.

QoS and/or fair queueing found in net/Kconfig

The configuration item CONFIG_NET_SCHED:

Help text

When the kernel has several packets to send out over a network device, it has to decide which ones to send first, which ones to delay, and which ones to drop. This is the job of the packet scheduler, and several different algorithms for how to do this "fairly" have been proposed.

If you say N here, you will get the standard packet scheduler, which is a FIFO (first come, first served). If you say Y here, you will be able to choose from among several alternative algorithms which can then be attached to different network devices. This is useful for example if some of your network devices are real time devices that need a certain minimum data flow rate, or if you need to limit the maximum data flow rate for traffic which matches specified criteria. This code is considered to be experimental.

To administer these schedulers, you'll need the user-level utilities from the package iproute2+tc at <ftp://ftp.tux.org/pub/net/ip-routing/>. That package also contains some documentation; for more, check out http://snafu.freedom.org/linux2.2/iproute-notes.html.

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 "QoS support", "Packet classifier API" and to some classifiers below. Documentation and software is at http://diffserv.sourceforge.net/.

If you say Y here and to "/proc file system" below, you will be able to read status information about packet schedulers from the file /proc/net/psched.

The available schedulers are listed in the following questions; you can say Y to as many as you like. If unsure, say N now.

Hardware

LKDDb

Raw data from LKDDb:

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

Automatic links from Google (and ads)

Custom Search

Popular queries:

Navigation: Linux Kernel Driver DataBase - web LKDDB: main index - N index

Automatically generated (in year 2024). See also LKDDb sources on GitLab