summaryrefslogtreecommitdiffstats
path: root/pimd/pim_cmd.c
diff options
context:
space:
mode:
authorStephen Hemminger <shemminger@vyatta.com>2009-08-19 17:25:52 +0000
committerDavid Lamparter <equinox@diac24.net>2010-02-05 01:40:34 +0100
commit590f04362a6dd546e868b5160a72443ce97547ca (patch)
tree95003d16232771d18ed45e4316533a55e04df31d /pimd/pim_cmd.c
parentc3c0726e61b0021e8177f42bcf71fb31c68e1a84 (diff)
downloadquagga-590f04362a6dd546e868b5160a72443ce97547ca.tar.bz2
quagga-590f04362a6dd546e868b5160a72443ce97547ca.tar.xz
zebra: rib update in background and recursive routes
Right now Zebra doesn't support recursive routes correctly when the next hop is a dynamic protocol. Imagine the case where a static route was entered to destination X.X.X.X via Y.Y.Y.Y and a protocol created a route to Y.Y.Y.Y. Any change from that protocol to Y.Y.Y.Y would might require zebra to update it's recursive route. The RIB as is doesn't have the necessary state to do this quickly, and the rib_update() and the resulting meta-queue is slow (2N) with lots of routes. That combined with the incremental updates from protocols makes the whole process potentially N^2. When we enabled it for BGP, the feed to 30min to complete. The comprimise I took was to start a delayed thread when zebra receives an update from protocol. So only a limited number of scans are done. I know this conflicts with your cleanup; but this might provide additional help. The existing meta-queue stuff makes the rib update worse not better.
Diffstat (limited to 'pimd/pim_cmd.c')
0 files changed, 0 insertions, 0 deletions