From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] Unable to run the second DPDK app: Cannot allocate memzone list
Date: Tue, 15 May 2018 11:46:03 +0100 [thread overview]
Message-ID: <33c27466-fe2b-8563-af56-7ffd340c0c3c@intel.com> (raw)
In-Reply-To: <6ed11b93-e1ff-6ea1-bb4b-dd88d33214cc@intel.com>
On 15-May-18 11:35 AM, Burakov, Anatoly wrote:
> On 15-May-18 11:24 AM, Andrew Rybchenko wrote:
>> Hi,
>>
>> starting from last night I cannot run the second DPDK app on the host.
>> I definitely have problems on Ubuntu 16.04.4 (Linux 4.4.0-124-generic)
>> and
>> RHEL 7.5 (Linux 3.10.0-862.el7.x86_64).
>> EAL command line option --file-prefix is used. So, it worked perfectly
>> before.
>> Not it fails in the following way:
>>
>> EAL: Detected 10 lcore(s)
>> EAL: Detected 1 NUMA nodes
>> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
>> EAL: Probing VFIO support...
>> EAL: VFIO support initialized
>> EAL: Cannot allocate memzone list
>> EAL: Cannot init memzone
>>
>> Memzone list allocation fails on flock() with errno "Resource
>> temporarily unavailable".
>>
>> Is it know? Any fixes available?
>>
>> Andrew.
>>
>
> Hi Andrew,
>
> I'm looking into it.
>
Hi Andrew,
http://dpdk.org/dev/patchwork/patch/40049/
Please verify if this fixes the issue.
--
Thanks,
Anatoly
prev parent reply other threads:[~2018-05-15 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 10:24 Andrew Rybchenko
2018-05-15 10:35 ` Burakov, Anatoly
2018-05-15 10:46 ` Burakov, Anatoly [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=33c27466-fe2b-8563-af56-7ffd340c0c3c@intel.com \
--to=anatoly.burakov@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).