From: Yan Fridland <yan@asocscloud.com>
To: Cliff Burdick <shaklee3@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK 19.11 can't work in a multi PRIMARY mode
Date: Mon, 6 Jul 2020 13:52:48 +0000 [thread overview]
Message-ID: <AM5PR10MB1668376256C30BA54852B9EFDF690@AM5PR10MB1668.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CA+Gp1nborqcguqrxhbM0=Rg-yraKnGgv-zqcG+-Kr0yEqukD+A@mail.gmail.com>
I’ve noticed that the string “--in-memory” is mandatory in this mode. However, it was not mentioned in the documentation in the website and the description was a bit not clear:
“Do not create any shared data structures and run entirely in memory.”
I must say that in EAL help its much clearer: “Operate entirely in memory. This will disable secondary process support”
Thanks,
Yan
From: Cliff Burdick <shaklee3@gmail.com>
Sent: Sunday, July 5, 2020 6:45 PM
To: Yan Fridland <yan@asocscloud.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK 19.11 can't work in a multi PRIMARY mode
Can you paste the whole command you're running? --file-prefix with unique strings afterward should allow you to do that.
On Sun, Jul 5, 2020 at 7:49 AM Yan Fridland <yan@asocscloud.com<mailto:yan@asocscloud.com>> wrote:
Hi Guys,
I am trying to use the --file-prefix to run several independent PRIMARY processes on the same VM (--proc-type=primary for all the processes).
The problem is that it doesn’t work and I am getting the following error:
"EAL: Cannot create lock on '/var/run/dpdk/rte/config'. Is another primary process running?"
Can anyone assist in resolving this issue ?
Thanks
Yan
prev parent reply other threads:[~2020-07-06 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 14:49 Yan Fridland
2020-07-05 15:45 ` Cliff Burdick
2020-07-05 18:03 ` Yan Fridland
2020-07-06 13:52 ` Yan Fridland [this message]
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=AM5PR10MB1668376256C30BA54852B9EFDF690@AM5PR10MB1668.EURPRD10.PROD.OUTLOOK.COM \
--to=yan@asocscloud.com \
--cc=shaklee3@gmail.com \
--cc=users@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).