table of contents
|ALTQ(4)||Device Drivers Manual||ALTQ(4)|
ALTQ — alternate
queuing of network packets
ALTQ framework provides several
disciplines for queuing outgoing network packets. This is done by
modifications to the interface packet queues. See altq(9)
The user interface for
ALTQ is implemented
by the pfctl(8) utility, so please refer to the
pfctl(8) and the pf.conf(5) manpages for
a complete description of the
ALTQ capabilities and
how to use it.
The following options in the kernel configuration file are related
- Build the “Class Based Queuing” discipline.
- Build the “Controlled Delay” discipline.
- Build the “Random Early Detection” extension.
- Build “Random Early Drop” for input and output.
- Build the “Hierarchical Packet Scheduler” discipline.
- Build the traffic conditioner. This option is meaningless at the moment as the conditioner is not used by any of the available disciplines or consumers.
- Build the “Priority Queuing” discipline.
- Build the “Fair Queuing” discipline.
- Required if the TSC is unusable.
- Enable additional debugging facilities.
ALTQ-disciplines cannot be
loaded as kernel modules. In order to use a certain discipline you have to
build it into a custom kernel. The pf(4) interface, that
is required for the configuration process of
can be loaded as a module.
The driver modifications described in altq(9)
are required to use a certain network card with
ALTQ. They have been applied to the following
hardware drivers: ae(4), age(4),
alc(4), ale(4), an(4),
de(4), ed(4), em(4),
et(4), fxp(4), gem(4),
ral(4), re(4), rl(4),
rum(4), sf(4), sge(4),
sis(4), sk(4), ste(4),
vr(4), vte(4), wi(4),
The ndis(4) framework also has support for
ALTQ and thus all encapsulated drivers.
The tun(4) and ng_iface(4)
pseudo drivers also do support
|July 24, 2015||Debian|