Re: fib/rib: allow storing void * instead of nexthop index

Hi Robin, On 31/07/2024 16:04, Robin Jarry wrote: Hi Vladimir, I noticed that the fib/rib APIs (both IPv4 and IPv6) require the next hops to be represented as integer indexes. Reading the code, I noticed that they are stored as uint64_t with the MSB used for internal purposes. I believe yo

fib/rib: allow storing void * instead of nexthop index

Hi Vladimir, I noticed that the fib/rib APIs (both IPv4 and IPv6) require the next hops to be represented as integer indexes. Reading the code, I noticed that they are stored as uint64_t with the MSB used for internal purposes. This require either having a contiguous array of nexthop objects