Hi Christian, <snip> > #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 > ^^^^^^^^^^^^^ Yes, I can see that from your output. Here however is my config: tc qdisc add dev eml_test root handle 1: prio bands 4 priomap 0 1 2 3 tc filter add dev eml_test parent 1:0 prio 1 protocol ip u32 match ip tos 0xb8 0xff flowid 1:1 tc filter add dev eml_test parent 1:0 prio 2 protocol ip u32 match ip tos 0x50 0xff flowid 1:2 tc filter add dev eml_test parent 1:0 prio 3 protocol ip u32 match ip tos 0x28 0xff flowid 1:3 tc filter add dev eml_test parent 1:0 prio 4 protocol ip u32 match ip tos 0x00 0xff flowid 1:4 tc qdisc add dev eml_test parent 1:1 handle 10: pfifo limit 2 tc qdisc add dev eml_test parent 1:2 handle 20: pfifo limit 2 tc qdisc add dev eml_test parent 1:3 handle 30: pfifo limit 2 tc qdisc add dev eml_test parent 1:4 handle 40: pfifo limit 2 ___ Here is what I see when issuing the same command: # tc -s -d qdisc list dev eml_test qdisc prio 1: bands 4 priomap 0 1 2 3 1 2 0 0 1 1 1 1 1 1 1 1 Sent 0 bytes 0 pkts (dropped 0, overlimits 0 requeues 0) qdisc pfifo 10: parent 1:1 limit 2p Sent 0 bytes 0 pkts (dropped 0, overlimits 0 requeues 0) qdisc pfifo 20: parent 1:2 limit 2p Sent 0 bytes 0 pkts (dropped 0, overlimits 0 requeues 0) qdisc pfifo 30: parent 1:3 limit 2p Sent 0 bytes 0 pkts (dropped 0, overlimits 0 requeues 0) qdisc pfifo 40: parent 1:4 limit 2p Sent 0 bytes 0 pkts (dropped 0, overlimits 0 requeues 0) > > > I have tried to configure PQ to have two queues per filter with no > success. > > What do you mean? Sorry, let me try to explain it this way (please refer to the above config): - I presently have -a strict PQ scheme which uses four queues - four filters each of which determine what type of traffic gets into which queue (EF, AF21, AF11 and BE respectively in my case) - a specific pFIFO qdisc for each PQ "class" __________ > > > 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 (see above) I already have something just like this, just with pfifo for each child as opposed to the prio listed in the above config (thanks in great part to your previous help). What I need is one more layer of hierarchy. Specifically, the queues defined by: 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 themselves need to be parents (e.g.): tc qdisc add dev eth1 parent 10:0 handle 11 prio tc qdisc add dev eth1 parent 20:0 handle 21 prio tc qdisc add dev eth1 parent 30:0 handle 31 prio > > Regards > /Christian > [ http://benve.info ] > > > _______________________________________________ > LARTC mailing list > LARTC@xxxxxxxxxxxxxxx > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
