> 'hfsc' can do this. > > in pf.conf manpage, read part for HFSC's '<sc>' > > if you want a connection to have high bandwidth for first 2 seconds, > then lower bandwidth after, you can use: > > hfsc( realtime( 20% 2000 5% ) upperlimit 100% ) > > % is relative to the bandwidth allocated to that queue in the hierarchy. > > upperlimit is an absolute maximum for the queue, even if no other queue > is busy. > > linkshare is the proportion the queue can receive when there is bandwidth > left over after all queues have received their realtime amount. > > realtime is the amount you want to guarantee to the queue no matter what. > > *please*, someone chime in and correct me if my "definitions" of upperlimit/ > linkshare/realtime are not correct. ( or if anything else i say is wrong, > i don't think i am wrong, but i do not insist i am right ) > > jared
As best I understand you are correct on how it works. http://www-2.cs.cmu.edu/~hzhang/HFSC/TALK/img041.GIF The presentation on HFSC at the parent page for that image explains a bit more about how hfsc works. I wish there was a better way to monitor the hfsc queues than pfctl -vvsq, because that doesn't provide detailed enough information (in my opinion). A important thing to remember about hfsc is that if you are distributing all of your bandwidth with 'realtime' your linkshare values will rarely come into play. If you are queuing hfsc on a low-bandwidth connection I suppose you might be better off using realtime by itself. Can anyone confirm/deny if I am correct with this? -hednod
