From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: thiery.ouattara@outscale.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: allow start two dpdk with no-huge option
Date: Tue, 10 Jul 2018 16:00:51 +0100 [thread overview]
Message-ID: <adf6ffb9-7817-1ec5-b0c1-7ee510f2d400@intel.com> (raw)
In-Reply-To: <1531234465-31339-1-git-send-email-thiery.ouattara@outscale.com>
On 10-Jul-18 3:54 PM, thiery.ouattara@outscale.com wrote:
> From: Kignelman OUATTARA <thiery.ouattara@outscale.com>
>
> in last version (v18.02), we was using no-huge option to
> start 2 dpdk instances simultanusly (for testing purpose).
>
> but since v18.05 when we start 2 instances:
> - the first dpdk app start normaly
> - the 2nd can't start because LOCK_EX option is set in
> flock(fd, LOCK_EX | LOCK_NB).
>
> So i did this patch to change LOCK_EX to LOCK_SH if no-huge
> option is set.
>
> Signed-off-by: Kignelman OUATTARA <thiery.ouattara@outscale.com>
> ---
Hi Kignelman,
I don't think this is safe to do. Even though hugepage memory is not
used, the --no-huge mode still stores page segments in fbarrays, so
while you would be able to *run* DPDK in such a scenario, the second
process would corrupt the memory of the first.
As a proper alternative, i would suggest looking at my --in-memory mode
patchset:
http://patches.dpdk.org/patch/40582/
http://patches.dpdk.org/patch/40583/
http://patches.dpdk.org/patch/40585/
http://patches.dpdk.org/patch/40584/
http://patches.dpdk.org/patch/40587/
http://patches.dpdk.org/patch/40586/
http://patches.dpdk.org/patch/40588/
http://patches.dpdk.org/patch/40590/
http://patches.dpdk.org/patch/40589/
This will solve the problem at its source.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-07-10 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 14:54 thiery.ouattara
2018-07-10 15:00 ` Burakov, Anatoly [this message]
2018-07-10 15:19 ` Thiery Ouattara
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=adf6ffb9-7817-1ec5-b0c1-7ee510f2d400@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=thiery.ouattara@outscale.com \
/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).