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 thru load_balance code). To my understanding it appears that ip4_lookup graph node has both the lookup and the next hop selection all bundled in one. If that is correct, then is the only way to try out alternate next hop selection algorithms be to create a graph node which is practically a clone of the ip4_lookup and then change the required portions in the cloned node code? If so, is this workflow in line with the way flexibility was intended? Any ideas welcome. Thanks -Venky #vnet
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20058): https://lists.fd.io/g/vpp-dev/message/20058 Mute This Topic: https://lists.fd.io/mt/85304201/21656 Mute #vnet:https://lists.fd.io/g/vpp-dev/mutehashtag/vnet Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
