On Mon, Dec 23, 2024 at 01:30:00PM -0800, Stephen Hemminger wrote: > On Mon, 23 Dec 2024 13:10:33 -0800 > Andre Muezerie <andre...@linux.microsoft.com> wrote: > > > From: Andre Muezerie <andre...@linux.microsoft.com> > > To: Vladimir Medvedkin <vladimir.medved...@intel.com> > > Cc: dev@dpdk.org, Andre Muezerie <andre...@linux.microsoft.com> > > Subject: [PATCH] app/test: fix stack overflow in fib6_perf_autotest > > Date: Mon, 23 Dec 2024 13:10:33 -0800 > > X-Mailer: git-send-email 1.8.3.1 > > > > Test fib6_perf_autotest was hitting a stack overflow on Windows > > with MSVC. > > > > The fix is to move some of the data from the stack to the heap. > > > > Signed-off-by: Andre Muezerie <andre...@linux.microsoft.com> > > Use regular malloc please. > rte_malloc comes from hugepages which are more limited and slower to > manipulate.
I recently submitted a patch for a test with a very similar issue and during review one of the reviewers encouraged me to use rte_calloc to allocate memory for the arrays, which I think makes sense (I had used malloc initially): https://inbox.dpdk.org/dev/20241218151206.ga25...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/ Even though this is a perf test, the code responsible for the memory allocations is not in the path for which time measurements are being taken (points between rte_rdtsc calls), so perf for the memory allocation code is probably not so critical. That being said, if you still feel strongly that malloc should be used instead let me know and I can make that change. Thanks, Andre Muezerie
