mirror of https://github.com/tLDP/LDP
long-standing DocBook validation errors corrected (thanks to FEDERICO BOLELLI)
This commit is contained in:
parent
de22a580b5
commit
dded5305f9
|
@ -41,9 +41,11 @@
|
|||
<section id="qs-fifo">
|
||||
<title>FIFO, First-In First-Out (&sch_pfifo; and &sch_bfifo;)</title>
|
||||
<note>
|
||||
<para>
|
||||
This is not the default qdisc on Linux interfaces. Be certain to see
|
||||
<xref linkend="qs-pfifo_fast"/> for the full details on the default
|
||||
(&sch_pfifo_fast;) qdisc.
|
||||
</para>
|
||||
</note>
|
||||
<para>
|
||||
The FIFO algorithm forms the basis for the default qdisc on all Linux
|
||||
|
|
|
@ -256,6 +256,7 @@
|
|||
any &linux-filter; could have a &linux-drop; action.
|
||||
</para>
|
||||
<note>
|
||||
<para>
|
||||
The only place in the Linux traffic control system where a packet can be
|
||||
explicitly dropped is a policer. A policer can limit packets enqueued
|
||||
at a specific rate, or it can be configured to drop all traffic matching
|
||||
|
@ -268,6 +269,7 @@
|
|||
<command>police rate 1bps burst 1 action drop/drop</command>.
|
||||
</para>
|
||||
</footnote>.
|
||||
</para>
|
||||
</note>
|
||||
<para>
|
||||
There are, however, places within the traffic control system where a
|
||||
|
|
|
@ -163,9 +163,11 @@
|
|||
Marking is a mechanism by which the packet is altered.
|
||||
</para>
|
||||
<note>
|
||||
<para>
|
||||
This is not &fwmark;. The &iptables; target &ipt-mark; and the
|
||||
&ipchains; &ipc-mark; are used to modify packet metadata, not the packet
|
||||
itself.
|
||||
</para>
|
||||
</note>
|
||||
<para>
|
||||
Traffic control marking mechanisms install a DSCP on the packet
|
||||
|
|
|
@ -57,8 +57,8 @@
|
|||
<para>
|
||||
<ulink url="http://opalsoft.net/qos/">General Quality of
|
||||
Service docs</ulink> (<emphasis>Leonardo Balliache</emphasis>)
|
||||
<para>
|
||||
</para>
|
||||
<para>
|
||||
There is a good deal of understandable and introductory documentation
|
||||
on his site, and in particular has some excellent overview material.
|
||||
See in particular, the detailed
|
||||
|
@ -169,12 +169,14 @@
|
|||
Mercilessly snipped from the main page of the DiffServ site...
|
||||
</para>
|
||||
<blockquote>
|
||||
<para>
|
||||
Differentiated Services (short: Diffserv) is an architecture for
|
||||
providing different types or levels of service for network traffic.
|
||||
One key characteristic of Diffserv is that flows are aggregated in
|
||||
the network, so that core routers only need to distinguish a
|
||||
comparably small number of aggregated flows, even if those flows
|
||||
contain thousands or millions of individual flows.
|
||||
</para>
|
||||
</blockquote>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
|
@ -55,8 +55,10 @@
|
|||
sort of queue is a &sch_fifo;.
|
||||
</para>
|
||||
<note>
|
||||
<para>
|
||||
The default qdisc under Linux is the &link-sch_pfifo_fast;, which is
|
||||
slightly more complex than the &link-sch_fifo;.
|
||||
</para>
|
||||
</note>
|
||||
<para>
|
||||
There are examples of queues in all sorts of software. The queue is a
|
||||
|
|
Loading…
Reference in New Issue