From bdavis@house.so14k.com  Fri Feb 25 21:17:40 2005
Return-Path: <bdavis@house.so14k.com>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B9B0116A4CE
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 25 Feb 2005 21:17:40 +0000 (GMT)
Received: from ender.liquidneon.com (ender.liquidneon.com [64.78.150.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 284A643D2D
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 25 Feb 2005 21:17:40 +0000 (GMT)
	(envelope-from bdavis@house.so14k.com)
Received: from localhost (localhost [127.0.0.1])
	by ender.liquidneon.com (Postfix) with ESMTP id 781EF442B
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 25 Feb 2005 14:17:39 -0700 (MST)
Received: from ender.liquidneon.com ([127.0.0.1])
 by localhost (ender.liquidneon.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 60095-04 for <FreeBSD-gnats-submit@freebsd.org>;
 Fri, 25 Feb 2005 14:17:39 -0700 (MST)
Received: from mccaffrey.house.so14k.com (gw.house.so14k.com [216.87.87.128])
	by ender.liquidneon.com (Postfix) with ESMTP id D9A8F41B2
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 25 Feb 2005 14:17:38 -0700 (MST)
Received: by mccaffrey.house.so14k.com (Postfix, from userid 1001)
	id DDDAEB8FA; Fri, 25 Feb 2005 14:17:37 -0700 (MST)
Message-Id: <20050225211737.DDDAEB8FA@mccaffrey.house.so14k.com>
Date: Fri, 25 Feb 2005 14:17:37 -0700 (MST)
From: Brad Davis <so14k@so14k.com>
Reply-To: Brad Davis <so14k@so14k.com>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: Add info on setting up ATLQ
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         78096
>Category:       docs
>Synopsis:       Add info on setting up ATLQ
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    simon
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Feb 25 21:20:08 GMT 2005
>Closed-Date:    Tue Mar 01 21:46:49 GMT 2005
>Last-Modified:  Tue Mar 01 21:46:49 GMT 2005
>Originator:     Brad Davis
>Release:        FreeBSD 5.4-PRERELEASE i386
>Organization:
>Environment:
System: FreeBSD mccaffrey.house.so14k.com 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #0: Thu Feb 24 17:03:44 MST 2005 root@mccaffrey.house.so14k.com:/usr/obj/usr/src/sys/SMP i386
>Description:
	After working with mlaier@, simon@ and trhodes@, this is what we came up with.
>How-To-Repeat:
>Fix:

--- doc-ori/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml	Fri Feb 25 13:31:41 2005
+++ doc/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml	Fri Feb 25 14:05:54 2005
@@ -198,7 +198,7 @@
   </sect1>
 
   <sect1 id="firewalls-pf">
-    <title>The Packet Filter (PF) Firewall</title>
+    <title>The Packet Filter (PF) Firewall and ALTQ</title>
 
     <indexterm>
       <primary>firewall</primary>
@@ -211,9 +211,9 @@
       contained <acronym>PF</acronym> as an integrated part of the
       base system was &os;&nbsp;5.3 in November 2004.
       <acronym>PF</acronym> is a complete, fully featured firewall
-      that contains <acronym>ALTQ</acronym> for bandwidth usage
-      management in a way similar to what DUMMYNET provides in
-      <acronym>IPFW</acronym>.  The OpenBSD project does an
+      that contains <acronym>ALTQ</acronym> (Alternate Queuing) for
+      bandwidth usage management in a way similar to what DUMMYNET
+      provides in <acronym>IPFW</acronym>.  The OpenBSD project does an
       outstanding job of maintaining the PF users' guide that it will
       not be made part of this handbook firewall section as that would
       just be duplicated effort.</para>
@@ -356,6 +356,61 @@
         enable the following option as well:</para>
 
       <programlisting>gateway_enable="YES"            # Enable as Lan gateway</programlisting>
+
+    </sect2>
+    <sect2>
+      <title>Enabling ALTQ</title>
+
+      <para>ALTQ is only avaliable by compiling the options into the
+        &os; Kernel.</para>
+
+      <para>ALTQ is not supported by all of the avaliable network card
+        drivers.  Please see the &man.altq.4; manual page for a list of
+        drivers that are supported in your release of &os;.
+
+    </sect2>
+    <sect2>
+      <title>ALTQ Kernel options</title>
+
+      <para>ALTQ is composed of many different parts to give the
+        functionality required.  The avaliable options are:</para>
+
+      <programlisting>options         ALTQ
+options         ALTQ_CBQ        # Class Bases Queuing
+options         ALTQ_RED        # Random Early Detection
+options         ALTQ_RIO        # RED In/Out
+options         ALTQ_HFSC       # Hierarchical Packet Scheduler
+options         ALTQ_PRIQ       # Priority Queuing
+options         ALTQ_NOPCC      # Required for SMP build</programlisting>
+
+      <para><literal>options ALTQ</literal> enables the ALTQ framework.</para>
+
+      <para><literal>options ALTQ_CBQ</literal> enables Class Based
+        Queuing (CBQ).  CBQ allows you to divide a connections's
+        bandwidth into different classes or queues.</para>
+
+      <para><literal>options ALTQ_RED</literal> enables Random Early
+        Detection (RED).  RED is used to avoid network congestion.  RED
+        does this by measuring the length of the queue and comparing
+        it to the minimum and maximum thresholds for the queue.  If the
+        queue is over the maximum all new packets will be dropped.  True
+        to its name, RED drops packets from different connections
+        randomly.</para>
+
+      <para><literal>options ALTQ_RIO</literal> enables Random Early
+        Detection In and Out.</para>
+
+      <para><literal>options ALTQ_HFSC</literal> enables Hierarchical
+        Fair Service Curve Packet Scheduler.  See <ulink
+        url="http://www-2.cs.cmu.edu/~hzhang/HFSC/main.html"></ulink>
+        for more info.</para>
+
+      <para><literal>options ALTQ_PRIQ</literal> enables Priority
+        Queuing (PRIQ).  PRIQ will always pass traffic that is in a
+        higher queue first.</para>
+
+      <para><literal>options ALTQ_NOPCC</literal> enables SMP support
+        for ALTQ.  This option is required on SMP systems.</para>
 
     </sect2>
   </sect1>
>Release-Note:
>Audit-Trail:

From: David Adam <zanchey@ucc.gu.uwa.edu.au>
To: Brad Davis <so14k@so14k.com>
Cc: FreeBSD-gnats-submit@FreeBSD.org, freebsd-doc@FreeBSD.org
Subject: Re: docs/78096: Add info on setting up ATLQ
Date: Sat, 26 Feb 2005 12:41:35 +0800 (WST)

 Hi Brad,
 
 Just one small nit,
 
 > +      <para><literal>options ALTQ_CBQ</literal> enables Class Based
 > +        Queuing (CBQ).  CBQ allows you to divide a connections's
 
 s/connections's/connection's/
 
 David Adam
 zanchey@
 

From: Tom Rhodes <trhodes@FreeBSD.org>
To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-doc@FreeBSD.org,
	Brad Davis <so14k@so14k.com>
Cc:  
Subject: Re: docs/78096: Add info on setting up ATLQ
Date: Sat, 26 Feb 2005 01:20:34 -0500

 Hi Brad,
 
 
 This is extremely useful and I agree we need it in the docs, but
 I have some comments on it.
 
 --- doc-ori/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml	Fri Feb 25 13:31:41 2005
 +++ doc/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml	Fri Feb 25 14:05:54 2005
 @@ -198,7 +198,7 @@
    </sect1>
  
    <sect1 id="firewalls-pf">
 -    <title>The Packet Filter (PF) Firewall</title>
 +    <title>The Packet Filter (PF) Firewall and ALTQ</title>
  
      <indexterm>
        <primary>firewall</primary>
 @@ -211,9 +211,9 @@
        contained <acronym>PF</acronym> as an integrated part of the
        base system was &os;&nbsp;5.3 in November 2004.
        <acronym>PF</acronym> is a complete, fully featured firewall
 -      that contains <acronym>ALTQ</acronym> for bandwidth usage
 -      management in a way similar to what DUMMYNET provides in
 -      <acronym>IPFW</acronym>.  The OpenBSD project does an
 +      that contains <acronym>ALTQ</acronym> (Alternate Queuing) for
 +      bandwidth usage management in a way similar to what DUMMYNET
 +      provides in <acronym>IPFW</acronym>.  The OpenBSD project does an
        outstanding job of maintaining the PF users' guide that it will
        not be made part of this handbook firewall section as that would
        just be duplicated effort.</para>
 
 Good, here is where we introduce what ALTQ stands for.  Now, I
 may be out of context, but what does it do?  :)
 
 @@ -356,6 +356,61 @@
          enable the following option as well:</para>
  
        <programlisting>gateway_enable="YES"            # Enable as Lan gateway</programlisting>
 +
 +    </sect2>
 +    <sect2>
 +      <title>Enabling ALTQ</title>
 +
 +      <para>ALTQ is only avaliable by compiling the options into the
 +        &os; Kernel.</para>
 +
 +      <para>ALTQ is not supported by all of the avaliable network card
 +        drivers.  Please see the &man.altq.4; manual page for a list of
 +        drivers that are supported in your release of &os;.
 
 Missing <para>, <acronym> tags here.
 
 These two can probably be merged together, something like:
 
 While <acronym>ALTQ</acronym> is a useful option ... explain why
 ... it is not yet supported by all network interface card
 drivers.  Please see the &man.altq.4; manual page for an up
 to date list on supported drivers.  To gain <acronym>ALTQ</acronym>
 support, the following options must be compiled into the kernel:
 
 Then list the kernel options, like you do here:
 
 
 +
 +      <programlisting>options         ALTQ
 +options         ALTQ_CBQ        # Class Bases Queuing
 +options         ALTQ_RED        # Random Early Detection
 +options         ALTQ_RIO        # RED In/Out
 +options         ALTQ_HFSC       # Hierarchical Packet Scheduler
 +options         ALTQ_PRIQ       # Priority Queuing
 +options         ALTQ_NOPCC      # Required for SMP build</programlisting>
 +
 +      <para><literal>options ALTQ</literal> enables the ALTQ framework.</para>
 +
 +      <para><literal>options ALTQ_CBQ</literal> enables Class Based
 +        Queuing (CBQ).  CBQ allows you to divide a connections's
 +        bandwidth into different classes or queues.</para>
 +
 +      <para><literal>options ALTQ_RED</literal> enables Random Early
 +        Detection (RED).  RED is used to avoid network congestion.  RED
 +        does this by measuring the length of the queue and comparing
 +        it to the minimum and maximum thresholds for the queue.  If the
 +        queue is over the maximum all new packets will be dropped.  True
 +        to its name, RED drops packets from different connections
 +        randomly.</para>
 +
 +      <para><literal>options ALTQ_RIO</literal> enables Random Early
 +        Detection In and Out.</para>
 +
 +      <para><literal>options ALTQ_HFSC</literal> enables Hierarchical
 +        Fair Service Curve Packet Scheduler.  See <ulink
 +        url="http://www-2.cs.cmu.edu/~hzhang/HFSC/main.html"></ulink>
 +        for more info.</para>
 +
 +      <para><literal>options ALTQ_PRIQ</literal> enables Priority
 +        Queuing (PRIQ).  PRIQ will always pass traffic that is in a
 +        higher queue first.</para>
 +
 +      <para><literal>options ALTQ_NOPCC</literal> enables SMP support
 +        for ALTQ.  This option is required on SMP systems.</para>
  
 
 This will give you better content in a single section in place
 of scattered information.
 
 And don't forget the other comment in the PR trail.  :)
 
 -- 
 Tom Rhodes

From: Brad Davis <so14k@so14k.com>
To: Tom Rhodes <trhodes@FreeBSD.org>,
	FreeBSD-gnats-submit@FreeBSD.org, freebsd-doc@FreeBSD.org,
	zanchey@ucc.gu.uwa.edu.au
Cc:  
Subject: Re: docs/78096: Add info on setting up ATLQ
Date: Sat, 26 Feb 2005 05:01:06 -0700

 Ok... How about this...
 
 
 --- doc-ori/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml	Fri Feb 25 13:31:41 2005
 +++ doc/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml	Sat Feb 26 04:13:55 2005
 @@ -198,7 +198,7 @@
    </sect1>
  
    <sect1 id="firewalls-pf">
 -    <title>The Packet Filter (PF) Firewall</title>
 +    <title>The Packet Filter (PF) Firewall and ALTQ</title>
  
      <indexterm>
        <primary>firewall</primary>
 @@ -211,12 +211,12 @@
        contained <acronym>PF</acronym> as an integrated part of the
        base system was &os;&nbsp;5.3 in November 2004.
        <acronym>PF</acronym> is a complete, fully featured firewall
 -      that contains <acronym>ALTQ</acronym> for bandwidth usage
 -      management in a way similar to what DUMMYNET provides in
 -      <acronym>IPFW</acronym>.  The OpenBSD project does an
 -      outstanding job of maintaining the PF users' guide that it will
 -      not be made part of this handbook firewall section as that would
 -      just be duplicated effort.</para>
 +      that contains <acronym>ALTQ</acronym> (Alternate Queuing).  ALTQ
 +      provides Quality of Service (QoS) bandwidth shaping that allows
 +      guaranteeing bandwidth to different services based on filtering
 +      rules.  The OpenBSD project does an outstanding job of maintaining
 +      the PF users' guide that it will not be made part of this handbook
 +      firewall section as that would just be duplicated effort.</para>
  
      <para>The availability of PF for the various &os; releases and versions is
        summarized below:</para>
 @@ -356,6 +356,55 @@
          enable the following option as well:</para>
  
        <programlisting>gateway_enable="YES"            # Enable as Lan gateway</programlisting>
 +
 +    </sect2>
 +    <sect2>
 +      <title>Enabling ALTQ</title>
 +
 +      <para><acronym>ALTQ</acronym> is only avaliable by compiling the
 +        options into the &os; Kernel.  <acronym>ALTQ</acronym> is not
 +        supported by all of the avaliable network card drivers.  Please
 +        see the &man.altq.4; manual page for a list of drivers that are
 +        supported in your release of &os;.  The following options will
 +        enable <acronym>ALTQ</acronym> and add additional functionality.
 +        </para>
 +
 +      <programlisting>options         ALTQ
 +options         ALTQ_CBQ        # Class Bases Queuing
 +options         ALTQ_RED        # Random Early Detection
 +options         ALTQ_RIO        # RED In/Out
 +options         ALTQ_HFSC       # Hierarchical Packet Scheduler
 +options         ALTQ_PRIQ       # Priority Queuing
 +options         ALTQ_NOPCC      # Required for SMP build</programlisting>
 +
 +      <para><literal>options ALTQ</literal> enables the ALTQ framework.</para>
 +
 +      <para><literal>options ALTQ_CBQ</literal> enables Class Based
 +        Queuing (CBQ).  CBQ allows you to divide a connection's
 +        bandwidth into different classes or queues.</para>
 +
 +      <para><literal>options ALTQ_RED</literal> enables Random Early
 +        Detection (RED).  RED is used to avoid network congestion.  RED
 +        does this by measuring the length of the queue and comparing
 +        it to the minimum and maximum thresholds for the queue.  If the
 +        queue is over the maximum all new packets will be dropped.  True
 +        to its name, RED drops packets from different connections
 +        randomly.</para>
 +
 +      <para><literal>options ALTQ_RIO</literal> enables Random Early
 +        Detection In and Out.</para>
 +
 +      <para><literal>options ALTQ_HFSC</literal> enables Hierarchical
 +        Fair Service Curve Packet Scheduler.  See <ulink
 +        url="http://www-2.cs.cmu.edu/~hzhang/HFSC/main.html"></ulink>
 +        for more info.</para>
 +
 +      <para><literal>options ALTQ_PRIQ</literal> enables Priority
 +        Queuing (PRIQ).  PRIQ will always pass traffic that is in a
 +        higher queue first.</para>
 +
 +      <para><literal>options ALTQ_NOPCC</literal> enables SMP support
 +        for ALTQ.  This option is required on SMP systems.</para>
  
      </sect2>
    </sect1>

From: Brad Davis <so14k@so14k.com>
To: Tom Rhodes <trhodes@FreeBSD.org>,
	FreeBSD-gnats-submit@FreeBSD.org, freebsd-doc@FreeBSD.org
Cc:  
Subject: Re: docs/78096: Add info on setting up ATLQ
Date: Sat, 26 Feb 2005 09:04:55 -0700

 After going over it again with remko@, here is a new diff.
 
 
 Brad
 
 
 --- doc-ori/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml	Fri Feb 25 13:31:41 2005
 +++ doc/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml	Sat Feb 26 08:54:37 2005
 @@ -198,7 +198,7 @@
    </sect1>
  
    <sect1 id="firewalls-pf">
 -    <title>The Packet Filter (PF) Firewall</title>
 +    <title>The OpenBSD Packet Filter (PF) and ALTQ</title>
  
      <indexterm>
        <primary>firewall</primary>
 @@ -211,12 +211,13 @@
        contained <acronym>PF</acronym> as an integrated part of the
        base system was &os;&nbsp;5.3 in November 2004.
        <acronym>PF</acronym> is a complete, fully featured firewall
 -      that contains <acronym>ALTQ</acronym> for bandwidth usage
 -      management in a way similar to what DUMMYNET provides in
 -      <acronym>IPFW</acronym>.  The OpenBSD project does an
 -      outstanding job of maintaining the PF users' guide that it will
 -      not be made part of this handbook firewall section as that would
 -      just be duplicated effort.</para>
 +      that has optional support for <acronym>ALTQ</acronym> (Alternate
 +      Queuing).  <acronym>ALTQ</acronym> provides Quality of Service
 +      (QoS) bandwidth shaping that allows guaranteeing bandwidth to
 +      different services based on filtering rules.  The OpenBSD
 +      project does an outstanding job of maintaining the PF User's
 +      Guide that it will not be made part of this handbook firewall
 +      section as that would just be duplicated effort.</para>
  
      <para>The availability of PF for the various &os; releases and versions is
        summarized below:</para>
 @@ -356,6 +357,57 @@
          enable the following option as well:</para>
  
        <programlisting>gateway_enable="YES"            # Enable as Lan gateway</programlisting>
 +
 +    </sect2>
 +    <sect2>
 +      <title>Enabling ALTQ</title>
 +
 +      <para><acronym>ALTQ</acronym> is only available by compiling the
 +        options into the &os; Kernel.  <acronym>ALTQ</acronym> is not
 +        supported by all of the available network card drivers.  Please
 +        see the &man.altq.4; manual page for a list of drivers that are
 +        supported in your release of &os;.  The following options will
 +        enable <acronym>ALTQ</acronym> and add additional functionality.
 +        </para>
 +
 +      <programlisting>options         ALTQ
 +options         ALTQ_CBQ        # Class Bases Queuing (CBQ)
 +options         ALTQ_RED        # Random Early Detection (RED)
 +options         ALTQ_RIO        # RED In/Out
 +options         ALTQ_HFSC       # Hierarchical Packet Scheduler (HFSC)
 +options         ALTQ_PRIQ       # Priority Queuing (PRIQ)
 +options         ALTQ_NOPCC      # Required for SMP build</programlisting>
 +
 +      <para><literal>options ALTQ</literal> enables the ALTQ framework.</para>
 +
 +      <para><literal>options ALTQ_CBQ</literal> enables Class Based
 +        Queuing (CBQ).  CBQ allows you to divide a connection's
 +        bandwidth into different classes or queues to prioritize
 +        traffic based on filter rules.</para>
 +
 +      <para><literal>options ALTQ_RED</literal> enables Random Early
 +        Detection (RED).  RED is used to avoid network congestion.  RED
 +        does this by measuring the length of the queue and comparing
 +        it to the minimum and maximum thresholds for the queue.  If the
 +        queue is over the maximum all new packets will be dropped.  True
 +        to its name, RED drops packets from different connections
 +        randomly.</para>
 +
 +      <para><literal>options ALTQ_RIO</literal> enables Random Early
 +        Detection In and Out.</para>
 +
 +      <para><literal>options ALTQ_HFSC</literal> enables the
 +        Hierarchical Fair Service Curve Packet Scheduler.  For more
 +        information about HFSC see: <ulink
 +        url="http://www-2.cs.cmu.edu/~hzhang/HFSC/main.html"></ulink>.
 +        </para>
 +
 +      <para><literal>options ALTQ_PRIQ</literal> enables Priority
 +        Queuing (PRIQ).  PRIQ will always pass traffic that is in a
 +        higher queue first.</para>
 +
 +      <para><literal>options ALTQ_NOPCC</literal> enables SMP support
 +        for ALTQ.  This option is required on SMP systems.</para>
  
      </sect2>
    </sect1>

From: Brad Davis <so14k@so14k.com>
To: Tom Rhodes <trhodes@FreeBSD.org>,
	FreeBSD-gnats-submit@FreeBSD.org, freebsd-doc@FreeBSD.org
Cc:  
Subject: Re: docs/78096: Add info on setting up ATLQ
Date: Sat, 26 Feb 2005 12:47:15 -0700

 More changes prodded by simon@...
 
 
 -Brad
 
 
 --- doc-ori/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml	Fri Feb 25 13:31:41 2005
 +++ doc/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml	Sat Feb 26 12:42:54 2005
 @@ -198,7 +198,7 @@
    </sect1>
  
    <sect1 id="firewalls-pf">
 -    <title>The Packet Filter (PF) Firewall</title>
 +    <title>The OpenBSD Packet Filter (PF) and ALTQ</title>
  
      <indexterm>
        <primary>firewall</primary>
 @@ -211,12 +211,13 @@
        contained <acronym>PF</acronym> as an integrated part of the
        base system was &os;&nbsp;5.3 in November 2004.
        <acronym>PF</acronym> is a complete, fully featured firewall
 -      that contains <acronym>ALTQ</acronym> for bandwidth usage
 -      management in a way similar to what DUMMYNET provides in
 -      <acronym>IPFW</acronym>.  The OpenBSD project does an
 -      outstanding job of maintaining the PF users' guide that it will
 -      not be made part of this handbook firewall section as that would
 -      just be duplicated effort.</para>
 +      that has optional support for <acronym>ALTQ</acronym> (Alternate
 +      Queuing).  <acronym>ALTQ</acronym> provides Quality of Service
 +      (<acronym>QoS</acronym>) bandwidth shaping that allows
 +      guaranteeing bandwidth to different services based on filtering
 +      rules.  The OpenBSD Project does an outstanding job of maintaining
 +      the PF User's Guide that it will not be made part of this handbook
 +      firewall section as that would just be duplicated effort.</para>
  
      <para>The availability of PF for the various &os; releases and versions is
        summarized below:</para>
 @@ -356,6 +357,57 @@
          enable the following option as well:</para>
  
        <programlisting>gateway_enable="YES"            # Enable as Lan gateway</programlisting>
 +
 +    </sect2>
 +    <sect2>
 +      <title>Enabling ALTQ</title>
 +
 +      <para><acronym>ALTQ</acronym> is only available by compiling the
 +        options into the &os; Kernel.  <acronym>ALTQ</acronym> is not
 +        supported by all of the available network card drivers.  Please
 +        see the &man.altq.4; manual page for a list of drivers that are
 +        supported in your release of &os;.  The following options will
 +        enable <acronym>ALTQ</acronym> and add additional functionality.
 +        </para>
 +
 +      <programlisting>options         ALTQ
 +options         ALTQ_CBQ        # Class Bases Queuing (CBQ)
 +options         ALTQ_RED        # Random Early Detection (RED)
 +options         ALTQ_RIO        # RED In/Out
 +options         ALTQ_HFSC       # Hierarchical Packet Scheduler (HFSC)
 +options         ALTQ_PRIQ       # Priority Queuing (PRIQ)
 +options         ALTQ_NOPCC      # Required for SMP build</programlisting>
 +
 +      <para><literal>options ALTQ</literal> enables the ALTQ framework.</para>
 +
 +      <para><literal>options ALTQ_CBQ</literal> enables Class Based
 +        Queuing (CBQ).  CBQ allows you to divide a connection's
 +        bandwidth into different classes or queues to prioritize
 +        traffic based on filter rules.</para>
 +
 +      <para><literal>options ALTQ_RED</literal> enables Random Early
 +        Detection (<acronym>RED</acronym>).  <acronym>RED</acronym> is
 +        used to avoid network congestion.  <acronym>RED</acronym> does
 +        this by measuring the length of the queue and comparing it to
 +        the minimum and maximum thresholds for the queue.  If the queue
 +        is over the maximum all new packets will be dropped.  True to
 +        its name, RED drops packets from different connections randomly.</para>
 +
 +      <para><literal>options ALTQ_RIO</literal> enables Random Early
 +        Detection In and Out.</para>
 +
 +      <para><literal>options ALTQ_HFSC</literal> enables the
 +        Hierarchical Fair Service Curve Packet Scheduler.  For more
 +        information about HFSC see: <ulink
 +          url="http://www-2.cs.cmu.edu/~hzhang/HFSC/main.html"></ulink>.
 +        </para>
 +
 +      <para><literal>options ALTQ_PRIQ</literal> enables Priority
 +        Queuing (PRIQ).  PRIQ will always pass traffic that is in a
 +        higher queue first.</para>
 +
 +      <para><literal>options ALTQ_NOPCC</literal> enables SMP support
 +        for ALTQ.  This option is required on SMP systems.</para>
  
      </sect2>
    </sect1>

From: Tom Rhodes <trhodes@FreeBSD.org>
To: Brad Davis <so14k@so14k.com>
Cc: FreeBSD-gnats-submit@FreeBSD.org, freebsd-doc@FreeBSD.org
Subject: Re: docs/78096: Add info on setting up ATLQ
Date: Sat, 26 Feb 2005 16:20:44 -0500

 On Sat, 26 Feb 2005 12:47:15 -0700
 Brad Davis <so14k@so14k.com> wrote:
 
 > More changes prodded by simon@...
 
 Wow, this reminds me of when I was a submitter.  I'll review in
 a bit, thanks!!
 
 -- 
 Tom Rhodes

From: "Simon L. Nielsen" <simon@FreeBSD.org>
To: Tom Rhodes <trhodes@FreeBSD.org>,
	FreeBSD-gnats-submit@FreeBSD.org, freebsd-doc@FreeBSD.org
Cc:  
Subject: Re: docs/78096: Add info on setting up ATLQ
Date: Sun, 27 Feb 2005 12:37:42 +0100

 --ey/N+yb7u/X9mFhi
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On 2005.02.26 12:47:15 -0700, Brad Davis wrote:
 > More changes prodded by simon@...
 
 [snip patch]
 
 This one does not apply for me... "Hunk #3 failed at 357.".. Could you
 recheck that it's good, and/or put it somewhere where it does not get
 mangled?
 
 
 --=20
 Simon L. Nielsen
 
 --ey/N+yb7u/X9mFhi
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.4 (FreeBSD)
 
 iD8DBQFCIbEGh9pcDSc1mlERAgj9AJ0ddb2eJf97P07POHD9ncLRY0p2oACeN9qZ
 M4fo0TolUS76d8JIfGU5PYs=
 =nIMs
 -----END PGP SIGNATURE-----
 
 --ey/N+yb7u/X9mFhi--

From: Brad Davis <so14k@so14k.com>
To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-doc@FreeBSD.org,
	"Simon L. Nielsen" <simon@FreeBSD.org>
Cc:  
Subject: Re: docs/78096: Add info on setting up ATLQ
Date: Mon, 28 Feb 2005 03:20:07 -0700

 Hi Simon,
 
 
 The latest version is here too:
 http://freebsd.so14k.com/firewall/altq-2005-02-26-12-43-22.patch
 
 Let me know if you have problems with this one.
 
 
 Regards,
 Brad Davis

From: "Simon L. Nielsen" <simon@FreeBSD.org>
To: FreeBSD-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: docs/78096: Add info on setting up ATLQ
Date: Mon, 28 Feb 2005 22:03:32 +0100

 --Sr1nOIr3CvdE5hEN
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On 2005.02.28 03:20:07 -0700, Brad Davis wrote:
 
 > The latest version is here too:
 > http://freebsd.so14k.com/firewall/altq-2005-02-26-12-43-22.patch
 >=20
 > Let me know if you have problems with this one.
 
 It still fails, are you sure it's generated against the latest CVS
 version? (1.46)
 
 --=20
 Simon L. Nielsen
 
 --Sr1nOIr3CvdE5hEN
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.4 (FreeBSD)
 
 iD8DBQFCI4cjh9pcDSc1mlERAjzfAJ9lAQu0l4sMYfrz1E9PE/I9h6yo9gCghGDx
 4YyhWvvalt+LVFBoFAQwwqs=
 =xbqg
 -----END PGP SIGNATURE-----
 
 --Sr1nOIr3CvdE5hEN--
Responsible-Changed-From-To: freebsd-doc->simon 
Responsible-Changed-By: simon 
Responsible-Changed-When: Tue Mar 1 21:13:32 GMT 2005 
Responsible-Changed-Why:  
I will get this committed. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=78096 
State-Changed-From-To: open->closed 
State-Changed-By: simon 
State-Changed-When: Tue Mar 1 21:46:39 GMT 2005 
State-Changed-Why:  
Committed, thanks! 

http://www.freebsd.org/cgi/query-pr.cgi?pr=78096 
>Unformatted:
