ise that you try and keep it this way by:
>
> 1 – choosing how the flow hash is calculated (see the list of ‘algorithms’
> available in ip_flow_hash_set)
>
> 2 – choosing in the CP how the buckets are populated.
>
>
>
> If 2. Is an option we can talk more about how you might go
Date: Tuesday, 7 September 2021 at 20:11
To: Neale Ranns
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Question regarding ip4/ip6 nexthop load balance
flexibility #vnet
Hi Neale,
Thanks for getting back. I thought as much that cloning code (even though I do
a graph node replacement) wouldn't h
e me some more detail on how you want to
> change the next-hop selection I will gladly give you some specific advice.
>
>
>
> /neale
>
>
>
>
>
> *From: *vpp-dev@lists.fd.io on behalf of Venky
> Venkatesh via lists.fd.io
> *Date: *Wednesday, 1 September
to change the next-hop selection
I will gladly give you some specific advice.
/neale
From: vpp-dev@lists.fd.io on behalf of Venky Venkatesh
via lists.fd.io
Date: Wednesday, 1 September 2021 at 16:48
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Question regarding ip4/ip6 nexthop load balance
Hi,
I am new to fd.io. So pls pardon my ignorance.
I wanted to experiment with different next hop selection algorithms once
the destination IP is looked up. I looked at the ip4 code. My changes would
be localized to how the nexthop is determined after the hash is calculated
(currently it is going
