On Fri, Jun 26, 2009 at 05:10:52PM +0200, Jarek Poplawski wrote:
So the idea is to balance memory and latency, so that large changes
(those affecting the root node) get at least one synchronize_rcu(),
while smaller changes just use call_rcu(), correct? This means that
the amount of memory awaiting an RCU grace period is limited, but
the algorithm avoids per-node synchronize_rcu() overhead.
If I understand the goal correctly, looks good! (Give or take my
limited understanding of fib_trie and is usage, of course.)
Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html