DPDK usage discussions
 help / color / mirror / Atom feed
* [dpdk-users] ring vdev and secondary process
@ 2018-09-03 14:40 Tom Barbette
  2018-09-03 15:08 ` Wiles, Keith
  0 siblings, 1 reply; 3+ messages in thread
From: Tom Barbette @ 2018-09-03 14:40 UTC (permalink / raw)
  To: users

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-users] ring vdev and secondary process
  2018-09-03 14:40 [dpdk-users] ring vdev and secondary process Tom Barbette
@ 2018-09-03 15:08 ` Wiles, Keith
  2018-09-05 11:19   ` Tom Barbette
  0 siblings, 1 reply; 3+ messages in thread
From: Wiles, Keith @ 2018-09-03 15:08 UTC (permalink / raw)
  To: Tom Barbette; +Cc: users



> On Sep 3, 2018, at 3:40 PM, Tom Barbette <barbette@kth.se> wrote:
> 
> 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.

Memory can not be allocated in the secondary process, but must request it from the primary. Is this the problem?

> 
> 
> 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

Regards,
Keith

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-users] ring vdev and secondary process
  2018-09-03 15:08 ` Wiles, Keith
@ 2018-09-05 11:19   ` Tom Barbette
  0 siblings, 0 replies; 3+ messages in thread
From: Tom Barbette @ 2018-09-05 11:19 UTC (permalink / raw)
  To: Wiles, Keith; +Cc: users

Hi Keith,

No it's not the problem. The ring is allocated by the primary. The secondary should just attach. Vdevs should be usable between multiple process from what I gathered.

Tom
________________________________________
De : Wiles, Keith <keith.wiles@intel.com>
Envoyé : lundi 3 septembre 2018 17:08
À : Tom Barbette
Cc : users@dpdk.org
Objet : Re: [dpdk-users] ring vdev and secondary process

> On Sep 3, 2018, at 3:40 PM, Tom Barbette <barbette@kth.se> wrote:
>
> 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.

Memory can not be allocated in the secondary process, but must request it from the primary. Is this the problem?

>
>
> 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

Regards,
Keith


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2018-09-05 11:19 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-09-03 14:40 [dpdk-users] ring vdev and secondary process Tom Barbette
2018-09-03 15:08 ` Wiles, Keith
2018-09-05 11:19   ` Tom Barbette

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).