Hello Dave, Just to follow up on this, we switched from 20.09 to 21.01 and that indeed seems to have solved the problem for us, having now run for about a month without the issue coming back.
Thanks for your help! Best regards, Elias On Sun, 2021-02-21 at 07:43 -0500, v...@barachs.net wrote: > That's right. In 20.09, bihash did its own os-level memory > allocation. You could (probably) pick up and port > src/vppinfra/bihash*.[ch] to 20.09, or you could add some config > knobs to the reassembly code. > > If switching to 21.01 is an option, that seems like the path of least > resistance. > > HTH... Dave > > -----Original Message----- > From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Elias > Rudberg > Sent: Friday, February 19, 2021 12:10 PM > To: v...@barachs.net; vpp-dev@lists.fd.io > Subject: Re: [vpp-dev] VPP 20.09 os_out_of_memory() in > clib_bihash_add_del_16_8 in IPv4 Shallow Virtual reassembly code > > Thanks Dave, however it looks like BIHASH_USE_HEAP does not exist in > VPP 20.09 but was introduced later. Looks like it appeared with the > commit 2454de2d4 "vppinfra: use heap to store bihash data" which was > after 20.09 was released. > > I guess this means that bihash data is not stored on the heap in VPP > 20.09. Maybe switching to VPP 21.01 would help with this issue then, > or at least with 21.01 all of our main heap space would need to be > consumed before we get another os_out_of_memory() SIGABRT crash? > > / Elias
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19022): https://lists.fd.io/g/vpp-dev/message/19022 Mute This Topic: https://lists.fd.io/mt/80753669/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
