DPDK patches and discussions
 help / color / mirror / Atom feed
From: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Query regarding multiple processes in DPDK
Date: Fri, 22 Nov 2013 18:20:07 +0530	[thread overview]
Message-ID: <C7CE7EEF248E2B48BBA63D0ABEEE700C45DFEF185F@GUREXMB01.ASIAN.AD.ARICENT.COM> (raw)

Hi guys,

The DPDP programmer's guide mentions -

===
The EAL also supports an auto-detection mode (set by EAL --proc-type=auto flag),
whereby an Intel(r) DPDK process is started as a secondary instance if a primary
instance is already running.
===

So does this mean that if I have a DPDK exe foo.out, then when I run the first instance of foo.out with -proc-type = auto, then foo.out will run as a primary process and when I spawn the second instance of foo.out (with first already running) again with -proc-type=auto, then this second instance automatically becomes secondary ?

Also is there any user code initialization change required or exactly the same code will work for both the processes ?

Regards
-Prashant






===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================

             reply	other threads:[~2013-11-22 12:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22 12:50 Prashant Upadhyaya [this message]
2013-11-22 13:31 ` Richardson, Bruce
2013-11-22 13:40   ` Prashant Upadhyaya
2013-11-22 13:46     ` Prashant Upadhyaya
2013-11-25  4:08       ` Prashant Upadhyaya
2013-11-25  9:29         ` Richardson, Bruce
2013-11-25 13:57           ` Prashant Upadhyaya
2013-11-25 19:55             ` Jeff Venable, Sr.

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=C7CE7EEF248E2B48BBA63D0ABEEE700C45DFEF185F@GUREXMB01.ASIAN.AD.ARICENT.COM \
    --to=prashant.upadhyaya@aricent.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).