From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0+5MKO=O6=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 671B01BE6B
 for <dev@dpdk.org>; Fri, 21 Dec 2018 19:24:35 +0100 (CET)
Received: from mail.lysator.liu.se (localhost [127.0.0.1])
 by mail.lysator.liu.se (Postfix) with ESMTP id D98A540014
 for <dev@dpdk.org>; Fri, 21 Dec 2018 19:24:34 +0100 (CET)
Received: by mail.lysator.liu.se (Postfix, from userid 1004)
 id C57FB40013; Fri, 21 Dec 2018 19:24:34 +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-90-98.mobileonline.telia.com
 [90.232.90.98])
 (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 29B4040004;
 Fri, 21 Dec 2018 19:24:33 +0100 (CET)
To: Venky Venkatesh <vvenkatesh@paloaltonetworks.com>,
 "dev@dpdk.org" <dev@dpdk.org>
References: <2D68DFF2-08A3-403B-9570-43D4AD916FD2@paloaltonetworks.com>
From: =?UTF-8?Q?Mattias_R=c3=b6nnblom?= <mattias.ronnblom@ericsson.com>
Message-ID: <e35340db-a364-4735-037d-c15220b3ecfe@ericsson.com>
Date: Fri, 21 Dec 2018 19:24:28 +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: <2D68DFF2-08A3-403B-9570-43D4AD916FD2@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, 21 Dec 2018 18:24:35 -0000

On 2018-12-21 06:13, Venky Venkatesh wrote:
> Hi,
> We are considering using a multi-process mode of the DPDK with the event generators and consumers being spread across multiple processes (on different cores). We are also considering using the DSW eventdev. Is the DSW designed for such a use case? If so, are there some restrictions and something specific that need to be done to make it work correctly?
> 

The purpose of an event device is to do dynamic load balancing across 
multiple cores. Using the DPDK multiple-process support, with its 
requirement of having unique, non-overlapping, core masks works against 
or even defeats this purpose.

Also, if you care about security, you don't want to disable ASLR.

That said, I can't see any immediate reason why it wouldn't work.