[ovs-dev] [PATCH v2 2/3] system-dpdk: use optimum hugepages for dpdk tests

Flavio Leitner fbl at sysclose.org
Thu May 21 04:33:32 UTC 2020


On Tue, May 19, 2020 at 12:23:40AM +0530, Gowrishankar Muthukrishnan wrote:
> >
> > >  dnl Find number of sockets
> > >  AT_CHECK([lscpu], [], [stdout])
> > > -AT_CHECK([cat stdout | grep "NUMA node(s)" | awk '{c=1; while
> > (c++<$(3)) {printf "512,"}; print "512"}' > NUMA_NODE])
> > > +AT_CHECK([cat stdout | grep "NUMA node(s)" | awk '{c=1; while
> > (c++<$(3)) {printf "448,"}; print "448"}' > NUMA_NODE])
> >
> > Why 448?
> >
> > When ovs dpdk is run with dpdk compatible drivers, its socket mem is set
> to (64MB + 512MB) per socket, otherwise only 64MB
> (for eg using dpdk virt devices) as far as the current tests require.
> 
> Testpmd app would need around ~338 MB (n_mbuf=155456, mbuf_size=2176) in
> its mempool, we would need in total:
> 64 MB (+ 512 MB) + 338 MB. I just rounded up the requirement for testpmd to
> 448 MB so that, we either configure 512 MB
> or 1GB in hugepage per socket.

Can you add a small comment saying that?

-- 
fbl


More information about the dev mailing list