tag:blogger.com,1999:blog-23021255.post8878097694651841377..comments2009-11-01T19:45:30.127+01:00Ivan Pepelnjakhttp://www.blogger.com/profile/13457151406311272386noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-23021255.post-5977197832770458562009-11-01T19:45:25.000+01:002009-11-01T19:45:25.000+01:00Oh, finally they started posting &quot;something&quot; detailed on CBWFQ (Be it HQF or pre-HQF) :) I remember i had to spend hours on simulation scenarios to find just how exactly CBWFQ works (which eventually appeared to be just WFQ with some steroids - ah well, they all come from GPS anyways :)<br /><br />However, I still cannot find any good explanation of pre-HQF: fair-queue + random-detect in class-default behavior in this article! <br /><br />Plus, I particularly enjoy this one: &quot;In pre-HQF IOS images, generally speaking, any class with a bandwidth command will generally be prioritized against classes without bandwidth or priority based on the classes’ Weight&quot;. There are so many details hidden behind this generally sound sentence ;)<br /><br />However, the good news is the slow progress towards unified queuing solution and configuration syntax for all platforms/link technologies. Wish one day this could be true for hardware-optimized systems ;)Petr Lapukhovnoreply@blogger.com