From: Petr Lapukhov (petr@internetworkexpert.com)
Date: Wed Oct 22 2008 - 02:40:01 ARST
Hi,
Since CBWFQ is just an "extension" of WFQ, interface-level "hold-queue"
command defines the maximum amount of buffers available to the scheduler. At
the same time, queue-limit under class-default sets the Congestive Discard
Threshold of WFQ. When configured under an individual class, queue-limit
defines the maximum size of this "flow" queue (FIFO queue). As for the
maximum number of dynamic flow queues, you set it with the command
"fair-queue" under class-default configuration. For more information on how
CBWFQ works, you may read our blog post:
http://blog.internetworkexpert.com/2008/08/17/insights-on-cbwfq/
HTH
-- Petr Lapukhov, CCIE #16379 (R&S/Security/SP/Voice) petr@internetworkexpert.comInternetwork Expert, Inc. http://www.InternetworkExpert.com Toll Free: 877-224-8987 Outside US: 775-826-4344
2008/10/20 ccievoice1 <ccievoice1@gmail.com>
> Hi all, > > Would like to ask, what is the relationship between queue-limit (configured > within a policy-map) and hold-queue (configured within interface) for a > CBWFQ? > > -- > Thanks and best regards > > > Blogs and organic groups at http://www.ccie.net > > _______________________________________________________________________ > Subscription information may be found at: > http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sat Nov 01 2008 - 15:35:21 ARST