Queuing disciplines

An interface section contains queuing discipline specifications, which consist of the name of the queuing discipline, an optional list of parameters, in parentheses and separated by commas, and an optional list of items attached to this queuing discipline, in curly braces.

In each interface section, one egress and one ingress queuing discipline can be defined.

Examples:

prio {
    class (1) ...;
    class (2) ...;
}

egress {
    ...
}

ingress {
    ...
}

The list of items can contain filters (if the queuing discipline supports them), classes (if the queuing discipline has classes), and further queuing disciplines.

The latter is mainly used for queuing disciplines like ingress or egress/dsmark^2.1, which have a ``central'' inner queuing discipline, but no queuing disciplines attached to classes. Example:

egress {
    ...
    fifo;
}