From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0+S2oJ=P2=ericsson.com=mattias.ronnblom@lysator.liu.se>
Received: from mail.lysator.liu.se (mail.lysator.liu.se [130.236.254.3])
 by dpdk.org (Postfix) with ESMTP id DB57914EC
 for <dev@dpdk.org>; Fri, 18 Jan 2019 15:36:26 +0100 (CET)
Received: from mail.lysator.liu.se (localhost [127.0.0.1])
 by mail.lysator.liu.se (Postfix) with ESMTP id 49FCE4001C
 for <dev@dpdk.org>; Fri, 18 Jan 2019 15:36:26 +0100 (CET)
Received: by mail.lysator.liu.se (Postfix, from userid 1004)
 id 363914000C; Fri, 18 Jan 2019 15:36:26 +0100 (CET)
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on
 bernadotte.lysator.liu.se
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 required=5.0 tests=ALL_TRUSTED,AWL
 autolearn=disabled version=3.4.1
X-Spam-Score: -0.9
Received: from [192.168.1.59] (host-90-232-24-238.mobileonline.telia.com
 [90.232.24.238])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mail.lysator.liu.se (Postfix) with ESMTPSA id 2D83F40008;
 Fri, 18 Jan 2019 15:36:25 +0100 (CET)
To: Venky Venkatesh <vvenkatesh@paloaltonetworks.com>,
 "dev@dpdk.org" <dev@dpdk.org>
References: <2D68DFF2-08A3-403B-9570-43D4AD916FD2@paloaltonetworks.com>
 <e35340db-a364-4735-037d-c15220b3ecfe@ericsson.com>
 <8C05BF3C-5D90-4CD0-AA71-1B4C4324E53B@paloaltonetworks.com>
 <597ee5d1-6db1-54ee-36af-df28ef1654bb@ericsson.com>
 <2ED77A34-B171-49BF-966A-BAE6A9E1BC66@paloaltonetworks.com>
 <ff0ca613-8a3c-b1d9-8247-fedf31aab884@ericsson.com>
 <58E15395-2C48-49C0-B702-40F511E61E55@paloaltonetworks.com>
From: =?UTF-8?Q?Mattias_R=c3=b6nnblom?= <mattias.ronnblom@ericsson.com>
Message-ID: <679c94fa-5274-8232-1a20-369f3cef47c0@ericsson.com>
Date: Fri, 18 Jan 2019 15:36:24 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <58E15395-2C48-49C0-B702-40F511E61E55@paloaltonetworks.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: Re: [dpdk-dev] DSW eventdev and multi-process DPDK
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jan 2019 14:36:27 -0000

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.