DPDK usage discussions
 help / color / mirror / Atom feed
From: Tom Barbette <barbette@kth.se>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] ring vdev and secondary process
Date: Mon, 3 Sep 2018 14:40:20 +0000	[thread overview]
Message-ID: <1535985620212.88927@kth.se> (raw)

Hi all,


I'm trying to use virtual devices (ring-based PMD, but the underlying system does not matter) between two DPDK processes.


But when I launch the secondary process, I get "RING: Cannot reserve memory". I modified the message to get the rte_errno, which is 17, File exists.  This also happens with testpmd.


I'm using DPDK 18.08. Using the ring API directly works without any problem. But I'd like to use the vdev one to build functional tests.


I tried with the TAP pmd, the device is not available in the secondary process (rte_eth_dev_count_avail() is 0).


Thanks,

Tom

             reply	other threads:[~2018-09-03 14:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 14:40 Tom Barbette [this message]
2018-09-03 15:08 ` Wiles, Keith
2018-09-05 11:19   ` Tom Barbette

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=1535985620212.88927@kth.se \
    --to=barbette@kth.se \
    --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).