Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug
report.
http://bugzilla.quagga.net/show_bug.cgi?id=431
------- Additional Comments From web@pilot.org.ua 2008-04-15 14:17 -------
This is an extract from 'sh ip ro' output, which demonstrates, that the new code
leads to nexthop calculation being done properly regardless of RIB updates
submission order and number of RIB records in each RN.
S 10.0.0.4/30 [1/0] via 192.168.3.1, vlan3900
C>* 10.0.0.4/30 is directly connected, em1
S 192.168.3.0/24 [1/0] via 10.0.0.6, em1
C>* 192.168.3.0/24 is directly connected, vlan3900
The setup is the same, which was used to generate output shown in comment #2.
RIB queue debugging shows the order of multi-queue processing:
2008/04/15 17:05:51 ZEBRA: rib_queue_add: 192.168.3.0/24: work queue added
2008/04/15 17:05:51 ZEBRA: rib_meta_queue_add: 192.168.3.0/24: queued rn
0x80a8340 into sub-queue 1
2008/04/15 17:05:51 ZEBRA: rib_meta_queue_add: 192.168.3.0/24: rn 0x80a8340 is
already queued in sub-queue 0
2008/04/15 17:05:51 ZEBRA: rib_queue_add: 192.168.3.0/24: rn 0x80a8340 queued
2008/04/15 17:05:51 ZEBRA: rib_queue_add: 10.0.0.4/30: work queue added
2008/04/15 17:05:51 ZEBRA: rib_meta_queue_add: 10.0.0.4/30: queued rn 0x80a2f40
into sub-queue 1
2008/04/15 17:05:51 ZEBRA: rib_meta_queue_add: 10.0.0.4/30: rn 0x80a2f40 is
already queued in sub-queue 0
2008/04/15 17:05:51 ZEBRA: rib_queue_add: 10.0.0.4/30: rn 0x80a2f40 queued
2008/04/15 17:05:51 ZEBRA: rib_process: 10.0.0.4/30: rn 0x80a2f40 dequeued
2008/04/15 17:05:51 ZEBRA: rib_process: 192.168.3.0/24: rn 0x80a8340 dequeued
2008/04/15 17:05:51 ZEBRA: rib_process: 192.168.3.0/24: rn 0x80a8340 dequeued
2008/04/15 17:05:51 ZEBRA: rib_process: 10.0.0.4/30: rn 0x80a2f40 dequeued
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
_______________________________________________
Quagga-bugs mailing list
Quagga-bugs@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-bugs
comments should be made in the comments box of this bug
report.
http://bugzilla.quagga.net/show_bug.cgi?id=431
------- Additional Comments From web@pilot.org.ua 2008-04-15 14:17 -------
This is an extract from 'sh ip ro' output, which demonstrates, that the new code
leads to nexthop calculation being done properly regardless of RIB updates
submission order and number of RIB records in each RN.
S 10.0.0.4/30 [1/0] via 192.168.3.1, vlan3900
C>* 10.0.0.4/30 is directly connected, em1
S 192.168.3.0/24 [1/0] via 10.0.0.6, em1
C>* 192.168.3.0/24 is directly connected, vlan3900
The setup is the same, which was used to generate output shown in comment #2.
RIB queue debugging shows the order of multi-queue processing:
2008/04/15 17:05:51 ZEBRA: rib_queue_add: 192.168.3.0/24: work queue added
2008/04/15 17:05:51 ZEBRA: rib_meta_queue_add: 192.168.3.0/24: queued rn
0x80a8340 into sub-queue 1
2008/04/15 17:05:51 ZEBRA: rib_meta_queue_add: 192.168.3.0/24: rn 0x80a8340 is
already queued in sub-queue 0
2008/04/15 17:05:51 ZEBRA: rib_queue_add: 192.168.3.0/24: rn 0x80a8340 queued
2008/04/15 17:05:51 ZEBRA: rib_queue_add: 10.0.0.4/30: work queue added
2008/04/15 17:05:51 ZEBRA: rib_meta_queue_add: 10.0.0.4/30: queued rn 0x80a2f40
into sub-queue 1
2008/04/15 17:05:51 ZEBRA: rib_meta_queue_add: 10.0.0.4/30: rn 0x80a2f40 is
already queued in sub-queue 0
2008/04/15 17:05:51 ZEBRA: rib_queue_add: 10.0.0.4/30: rn 0x80a2f40 queued
2008/04/15 17:05:51 ZEBRA: rib_process: 10.0.0.4/30: rn 0x80a2f40 dequeued
2008/04/15 17:05:51 ZEBRA: rib_process: 192.168.3.0/24: rn 0x80a8340 dequeued
2008/04/15 17:05:51 ZEBRA: rib_process: 192.168.3.0/24: rn 0x80a8340 dequeued
2008/04/15 17:05:51 ZEBRA: rib_process: 10.0.0.4/30: rn 0x80a2f40 dequeued
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
_______________________________________________
Quagga-bugs mailing list
Quagga-bugs@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-bugs