* Damian Gerow <[EMAIL PROTECTED]> wrote: > The man page dictates that priq doesn't do bandwidth shaping, yet to define > a priq queue, you have to declare the bandwidth available. So which is it?
How does the man page dictate (or even imply) that priq doesn't use the bandwidth parameter? As I understand it, priq only affects things at all when a queue is exceeding its bandwidth limit. As long as a queue is below the limit, it does ABSOLUTELY NOTHING. Only when the limit is exceeded, priq drops packets instead of sending them out, picking which packets to drop based on the priorities. It DOES NOT send out packets in an order (based on priorities) other than the one they were queued in, while the bandwidth limit is not reached. Hence, its entire operation is defined through the bandwidth parameter, and without any defined bandwidth limit, it couldn't do anything at all. > When defining the queue, it's the same available bandwidth for both ingress > and egress traffic. What happens to asynchronous links? There are no inbound queues in ALTQ. Incoming packets are simply not queued at all, and ALTQ does not in any way affect them or count them towards anything. Therefore this is not an issue. Daniel
