Thanks for hacking and improving and the trie... another idea that could
be also tested. If we look into routing table we see that most leafs
only has one prefix
Main:
Aver depth: 2.57
Max depth: 7
Leaves: 231173
ip route | wc -l
241649
Thats 231173/241649 = 96% with the current Internet routing.
How about if would have a fastpath and store one entry direct in the
leaf struct this to avoid loading the leaf_info list in most cases?
One could believe that both lookup and dump could improve.
Cheers.
--ro
Stephen Hemminger writes:
> Remember that the code should be optimized for lookup, not management
> operations. We ran into this during testing (the test suite was looking
> for number of routes), thats why I put in the size field.
>
> The existing dump code is really slow:
>
> 1) FIB_TRIE Under KVM:
> load 164393 routes 12.436 sec
> ip route | wc -l 12.569 sec
> grep /proc/net/route 25.357 sec
>
> 99% of the cpu time is spent in nextleaf() during these dump operations.
>
> 2) FIB_HASH Under KVM:
> load 164393 routes 10.833 sec
> ip route | wc -l 1.981 sec
> grep /proc/net/route 0.204 sec
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
