On Fri, 2013-12-13 at 15:59 -0800, Andy Grover wrote:
Instead of an array, use a rbtree. Less memory use on average, and
can allow 255 entries. We go from O(1) to O(log n) on lookups. If this
shows up on profiling (it won't) then transition to other kernel lookup
methods is straightforward
On 12/16/2013 01:40 PM, Nicholas A. Bellinger wrote:
On Fri, 2013-12-13 at 15:59 -0800, Andy Grover wrote:
Instead of an array, use a rbtree. Less memory use on average, and
can allow 255 entries. We go from O(1) to O(log n) on lookups. If this
shows up on profiling (it won't) then transition
On Mon, 2013-12-16 at 17:00 -0800, Andy Grover wrote:
On 12/16/2013 01:40 PM, Nicholas A. Bellinger wrote:
On Fri, 2013-12-13 at 15:59 -0800, Andy Grover wrote:
Instead of an array, use a rbtree. Less memory use on average, and
can allow 255 entries. We go from O(1) to O(log n) on lookups.
Instead of an array, use a rbtree. Less memory use on average, and
can allow 255 entries. We go from O(1) to O(log n) on lookups. If this
shows up on profiling (it won't) then transition to other kernel lookup
methods is straightforward from here.
Change core_disable_device_list_for_node to be
4 matches
Mail list logo
