On Tue, 2023-08-15 at 10:45 -0700, Stephen Hemminger wrote: > > Why? > > It is not always ideal to reinitialize a DPDK process. Memory needs > > to be reinitialized, hugetables need to warm up etc. > > > > > I am familiar with the backstory of why this is desirable in your > case. > > But others may not be. It will work for you, but for the wider the > > range of libraries and drivers it probably won't. > >
Fair enough. > > As a compromise, can this restart be officially tagged as > unsupported. any pointers how to do this? I have no idea how to mark something unsupported in code. If this is acceptable in cover letter, I'm happy to do that too. > > I.e. it may work for some drivers and libraries but not all of them. > > If nothing else many parts of DPDK still do leak memory on cleanup > > and currently this is harmless. > > > > This has enough impact that it probably needs to wait past 23.11 > release. > > Sure, no rush. Happy to wait for time slot and accumulate review feedbacks. > > Could you add a test for restart into standalone tests and test-pmd? Will do.
