2009/5/21, Fabio Marcone <fabio.marcone@xxxxxxx>: > Hi, > > > > Different priorities are actual for filters with the same parent, > > lower ones are looking first. > > > > > ok > > > Check output: > > tc -s filter show dev eth0 > > and > > tc -s qdisc show dev eth0 > > > > > # tc -s -d qdisc show dev eth0 > qdisc prio 1: bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 > Sent 7021292 bytes 4684 pkt (dropped 0, overlimits 0 requeues 0) > rate 0bit 0pps backlog 0b 0p requeues 0 > qdisc sfq 2: parent 1:1 limit 128p quantum 1514b flows 128/1024 perturb > 10sec > Sent 2997906 bytes 2003 pkt (dropped 0, overlimits 0 requeues 0) > rate 0bit 0pps backlog 0b 0p requeues 0 > qdisc sfq 3: parent 1:2 limit 128p quantum 1514b flows 128/1024 perturb > 10sec > Sent 720 bytes 8 pkt (dropped 0, overlimits 0 requeues 0) > rate 0bit 0pps backlog 0b 0p requeues 0 > qdisc sfq 4: parent 1:3 limit 128p quantum 1514b flows 128/1024 perturb > 10sec > Sent 4022666 bytes 2673 pkt (dropped 0, overlimits 0 requeues 0) > rate 0bit 0pps backlog 0b 0p requeues 0 > > # tc -s -d class show dev eth0 > class prio 1:1 parent 1: leaf 2: > Sent 2997906 bytes 2003 pkt (dropped 0, overlimits 0 requeues 0) > backlog 0b 0p requeues 0 > class prio 1:2 parent 1: leaf 3: > Sent 6082 bytes 49 pkt (dropped 0, overlimits 0 requeues 0) > backlog 0b 0p requeues 0 > class prio 1:3 parent 1: leaf 4: > Sent 4022666 bytes 2673 pkt (dropped 0, overlimits 0 requeues 0) > backlog 0b 0p requeues 0 > > > you see, class with higher priority sent less packets than class 1:3 (with > lower priority). This is the proof that something is wrong, or I fall in > error? > > class 1:2 receive packets from a ssh connection, used for test. > > > Thanks, > Fabio > I need additional info: iptables -S iptables -S -t mangle and tc -s filter show dev eth0. There must be something wrong in your packet marking scheme. What is your test environment? -- Best regards Anatoly Muliarski -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
