Re: [ovs-dev] [PATCH ovn] Start mcast id allocations from OVN_MIN_IP_MULTICAST.

2024-04-12 Thread Ihar Hrachyshka
On Fri, Apr 12, 2024 at 10:33 AM Dumitru Ceara wrote: > On 4/11/24 10:32, Ales Musil wrote: > > On Thu, Apr 4, 2024 at 11:44 PM Ihar Hrachyshka > wrote: > > > >> Strictly speaking, this is not *essential* to start from MIN and not > >> MIN+1 (once the hint reaches max, it will wrap back to MIN

Re: [ovs-dev] [PATCH ovn] Start mcast id allocations from OVN_MIN_IP_MULTICAST.

2024-04-12 Thread Dumitru Ceara
On 4/11/24 10:32, Ales Musil wrote: > On Thu, Apr 4, 2024 at 11:44 PM Ihar Hrachyshka wrote: > >> Strictly speaking, this is not *essential* to start from MIN and not >> MIN+1 (once the hint reaches max, it will wrap back to MIN anyway), but >> this is inconsistent with how we handle datapath

Re: [ovs-dev] [PATCH ovn] Start mcast id allocations from OVN_MIN_IP_MULTICAST.

2024-04-11 Thread Ales Musil
On Thu, Apr 4, 2024 at 11:44 PM Ihar Hrachyshka wrote: > Strictly speaking, this is not *essential* to start from MIN and not > MIN+1 (once the hint reaches max, it will wrap back to MIN anyway), but > this is inconsistent with how we handle datapath and port keys (we start > with hint = 0

[ovs-dev] [PATCH ovn] Start mcast id allocations from OVN_MIN_IP_MULTICAST.

2024-04-04 Thread Ihar Hrachyshka
Strictly speaking, this is not *essential* to start from MIN and not MIN+1 (once the hint reaches max, it will wrap back to MIN anyway), but this is inconsistent with how we handle datapath and port keys (we start with hint = 0 there). Signed-off-by: Ihar Hrachyshka --- northd/northd.c | 3 ++-