Hi,
> > Your config does not prevent an higher priority class from starving
> > a lower priority class.
>
> Exactly. That is requirement.
OK
> Those stats are nice to have, but the ones I must have are for how many
> bytes/packets are enqueued at whatever time I check the queues.
That information is there. Here is an example:
(b=bytes p=packets)
#tc -s -d qdisc list dev eth1
qdisc prio 1: root bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 85357186 bytes 59299 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 35p requeues 0
+-> This field is not initialized for this
qdisc type
qdisc pfifo 10: parent 1:1 limit 1000p
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
^^^^^^^^^^^^^
qdisc pfifo 20: parent 1:2 limit 1000p
Sent 85357120 bytes 59298 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 50470b 35p requeues 0
^^^^^^^^^^^^^^^^^^
qdisc pfifo 30: parent 1:3 limit 1000p
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
^^^^^^^^^^^^^
> I have tried to configure PQ to have two queues per filter with no success.
What do you mean?
> Is it even possible to have (what I'll call) hierarchical PQ? I have yet to
> find it.
Something like this?
tc qdisc add dev eth1 handle 1: root prio
tc qdisc add dev eth1 parent 1:1 handle 10 prio
tc qdisc add dev eth1 parent 1:2 handle 20 prio
tc qdisc add dev eth1 parent 1:3 handle 30 prio
Regards
/Christian
[ http://benve.info ]
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
