DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] DPDK library grab all the memory during start up
@ 2016-03-11  2:46 John Wei
  0 siblings, 0 replies; only message in thread
From: John Wei @ 2016-03-11  2:46 UTC (permalink / raw)
  To: dev

I am setting up open-vswitch with DPDK in container, and running many this
OVS/DPDK containers on the same host.
OVS in each container will be using differ PCI deviced bound to DPDK.
I am using --file-prefix to allow sharing of same /dev/hugepages tlbfs, and
using --socket-mem to limit the memory used by each OVS.
But, DPDK library first grab all the available memory, pick the best
memory, before releasing memory not needed. It seems tat this process is
serialized.
Each DPDK app will need to wait the previous app to complete that process,
before next app can start grabing, picking, and releasing memory.
This is taking a long time when you try to start many DPDK app in parallel.
I tried to use different tlbfs for each app, and limit each tlbfs with
nr_inodes, but that does not work.

Any suggestion on addressing this issue? Is there way to tell DPDK library
not to grab so much memory?

John

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2016-03-11  2:46 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-03-11  2:46 [dpdk-dev] DPDK library grab all the memory during start up John Wei

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).