Re: [ovs-dev] [PATCH v2 1/3] system-dpdk: cleanup stale hugepage files after tests

2020-05-26 Thread Gowrishankar Muthukrishnan
I tried --in-memory but finding issues with existing tests unable to pass mainly, being unable to ping between kernel veth and dpdk tap. Problem could be because of implicit --no-shconf ? .Can we handle this separately as it is blocking other patches ? Your opinions please. Regards. On Thu, May 2

Re: [ovs-dev] [PATCH v2 1/3] system-dpdk: cleanup stale hugepage files after tests

2020-05-21 Thread Ilya Maximets
On 5/16/20 7:53 AM, Gowrishankar Muthukrishnan wrote: > After dpdk tests completes, cleaning up hugepage map files > created by tests is helpful to release used memory into > hugepage memory allocator. > > Signed-off-by: Gowrishankar Muthukrishnan > --- > tests/system-dpdk-macros.at | 13 +++

Re: [ovs-dev] [PATCH v2 1/3] system-dpdk: cleanup stale hugepage files after tests

2020-05-18 Thread Flavio Leitner
On Sat, May 16, 2020 at 11:23:51AM +0530, Gowrishankar Muthukrishnan wrote: > After dpdk tests completes, cleaning up hugepage map files > created by tests is helpful to release used memory into > hugepage memory allocator. > > Signed-off-by: Gowrishankar Muthukrishnan > --- > tests/system-dpdk-

[ovs-dev] [PATCH v2 1/3] system-dpdk: cleanup stale hugepage files after tests

2020-05-15 Thread Gowrishankar Muthukrishnan
After dpdk tests completes, cleaning up hugepage map files created by tests is helpful to release used memory into hugepage memory allocator. Signed-off-by: Gowrishankar Muthukrishnan --- tests/system-dpdk-macros.at | 13 + tests/system-dpdk.at| 7 +++ 2 files changed, 2