From: John Wei <johntwei@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] DPDK library grab all the memory during start up
Date: Thu, 10 Mar 2016 18:46:42 -0800 [thread overview]
Message-ID: <CAGaeUpoq88U4mSYx5e64=cbxRqddq_Zte3-j1Vss-22mo=UyJA@mail.gmail.com> (raw)
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
reply other threads:[~2016-03-11 2:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGaeUpoq88U4mSYx5e64=cbxRqddq_Zte3-j1Vss-22mo=UyJA@mail.gmail.com' \
--to=johntwei@gmail.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).