From: Mauro Annarumma <mauroannarumma@hotmail.it>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Question on DPDK multi-process support
Date: Mon, 17 Feb 2014 16:48:10 +0100 [thread overview]
Message-ID: <DUB111-W112B183AFF254C3D2444AE2B1990@phx.gbl> (raw)
Hi,
I have some doubts on the DPDK multi-process support:
1) According to the Programmers Guide (pag. 109 - 20.3 Multi-process Limitations), one of the multi-process limitations is:
"All Intel® DPDK processes running as a single application and using shared memory must have distinct coremask arguments. It is not possible to have a primary and secondary instance, or two secondary instances, using any of the same logical cores. Attempting to do so can cause corruption of memory pool caches, among other issues."
Does it mean that I can run a number of DPDK processes at most equal to the number of my CPU logical cores? In the case I run 2 mono-lcore DPDK processes with the same coremask, what are the possible issues?
2) Can a secondary process use the rte_eth_rx_burst over a queue of a NIC port configured in the primary process?
Regards,
Mauro
next reply other threads:[~2014-02-17 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 15:48 Mauro Annarumma [this message]
2014-02-17 16:44 ` Richardson, Bruce
2014-02-18 12:45 ` Mauro Annarumma
2014-02-18 12:53 ` Richardson, Bruce
2014-02-18 13:14 ` [dpdk-dev] Receive queue full François-Frédéric Ozog
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=DUB111-W112B183AFF254C3D2444AE2B1990@phx.gbl \
--to=mauroannarumma@hotmail.it \
--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).