From: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
To: Venky Venkatesh <vvenkatesh@paloaltonetworks.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DSW eventdev and multi-process DPDK
Date: Fri, 18 Jan 2019 15:47:42 +0100 [thread overview]
Message-ID: <b9c363d6-f64f-d9a3-8e25-3d06c80e1024@ericsson.com> (raw)
In-Reply-To: <C87F4808-2A33-47E0-B959-B95895B19D2F@paloaltonetworks.com>
On 2019-01-18 07:36, Venky Venkatesh wrote:
>
> [VV]: Some more information. I went with the assumption that I will call these APIs on both the PRIMARY and SECONDARY processes and that these APIs would do the right thing viz. on the PRIMARY it would allocate and initialize while in the SECONDARY it would attach to those memories and structures. However that doesn’t seem to be the case: rte_event_port_setup is trying to allocate a ring of the same name in both processes and is crashing in rte_memzone_reserve_thread_safe (specifically at if ((memzone_lookup_thread_unsafe(name)) != NULL)) which is called from rte_event_ring_create.
Ports etc need (and should) only be configured once.
> Can you pls advise if the DSW is multiprocess ready?
I've answered this question already.
>If not, are there any plans to do so?
>
For all I know, it should work already. If not, maybe it's here Palo
Alto Networks chips in.
next prev parent reply other threads:[~2019-01-18 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 5:13 Venky Venkatesh
2018-12-21 18:24 ` Mattias Rönnblom
2018-12-21 18:34 ` Venky Venkatesh
2018-12-21 18:59 ` Mattias Rönnblom
2018-12-21 19:12 ` Venky Venkatesh
2019-01-07 15:36 ` Mattias Rönnblom
2019-01-17 19:10 ` Venky Venkatesh
2019-01-18 6:36 ` Venky Venkatesh
2019-01-18 14:47 ` Mattias Rönnblom [this message]
2019-01-18 14:36 ` Mattias Rönnblom
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=b9c363d6-f64f-d9a3-8e25-3d06c80e1024@ericsson.com \
--to=mattias.ronnblom@ericsson.com \
--cc=dev@dpdk.org \
--cc=vvenkatesh@paloaltonetworks.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).