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:36:24 +0100 [thread overview]
Message-ID: <679c94fa-5274-8232-1a20-369f3cef47c0@ericsson.com> (raw)
In-Reply-To: <58E15395-2C48-49C0-B702-40F511E61E55@paloaltonetworks.com>
On 2019-01-17 20:10, Venky Venkatesh wrote:
> [VV]: I had a question on the eventdev initialization API in the above multi-process setting. The following are the objects and API to init each of them. For each of these can you confirm whether it needs to be called in the PRIMARY process only or even the SECONDARY process must call these. The reason for the question is that the shared memory must be safely initialized once.
>
> Event device itself: rte_event_dev_configure, rte_event_dev_start
> Ports: rte_event_port_setup
> Queues: rte_event_queue_setup
> Port-Queue-Links: rte_event_port_link
>
I don't think it matters if those calls are made from the primary or
secondary process. Please note however, those call are not thread-safe,
so external synchronization is required the calls are made from multiple
threads/processes.
prev parent reply other threads:[~2019-01-18 14:36 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
2019-01-18 14:36 ` Mattias Rönnblom [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=679c94fa-5274-8232-1a20-369f3cef47c0@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).