Due to overhead, you won't be able to allocate 0xffffffff bytes (4gb-1), but in the size range you're describing there are no known first-order obvious problem with the memory allocator.
I don't blame you for asking, but I'm afraid it's likely that you have a dangling reference in your app code or some such to chase down... D. -----Original Message----- From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Prashant Upadhyaya Sent: Friday, February 8, 2019 8:21 AM To: vpp-dev@lists.fd.io Subject: [vpp-dev] Regarding clib_mem_alloc Hi, Assuming the heap is sufficiently dimensioned, can any size be requested from clib_mem_alloc which fits in u32 ? Are there any issues if higher sizes are requested eg. can clib_mem_alloc actually return a pointer but the allocated size is not as much as the requested size ? Perhaps it is bizarre to ask the above, but one of my usecases works nicely when I request a size of around 216 MB, but runs into application level corruption when I request double of this i.e. around 432 MB. So thought of asking. It could by all means be and likely is an application level problem. This is with VPP 18.01 Regards -Prashant
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12220): https://lists.fd.io/g/vpp-dev/message/12220 Mute This Topic: https://lists.fd.io/mt/29701184/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
