From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0+Rx6p=O4=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 EF07A1B5BB
 for <dev@dpdk.org>; Wed, 19 Dec 2018 21:02:50 +0100 (CET)
Received: from mail.lysator.liu.se (localhost [127.0.0.1])
 by mail.lysator.liu.se (Postfix) with ESMTP id 710BA4000C
 for <dev@dpdk.org>; Wed, 19 Dec 2018 21:02:50 +0100 (CET)
Received: by mail.lysator.liu.se (Postfix, from userid 1004)
 id 5B01B40009; Wed, 19 Dec 2018 21:02:50 +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-140-56.mobileonline.telia.com
 [90.232.140.56])
 (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 7414340005;
 Wed, 19 Dec 2018 21:02:49 +0100 (CET)
To: Venky Venkatesh <vvenkatesh@paloaltonetworks.com>,
 "dev@dpdk.org" <dev@dpdk.org>
References: <567E74E5-FB59-45EB-AE3D-D16E502D8F1C@paloaltonetworks.com>
 <2de30142-6d88-4b54-7fcb-b98bbccb951a@ericsson.com>
 <C287A243-DA6A-4D40-8D70-35FAE201F074@paloaltonetworks.com>
From: =?UTF-8?Q?Mattias_R=c3=b6nnblom?= <mattias.ronnblom@ericsson.com>
Message-ID: <f8f4a3da-cd25-d816-12d9-e7bbb3791912@ericsson.com>
Date: Wed, 19 Dec 2018 21:02:48 +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: <C287A243-DA6A-4D40-8D70-35FAE201F074@paloaltonetworks.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: Re: [dpdk-dev] Eventdev DSW and eth_rx_adapters
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: Wed, 19 Dec 2018 20:02:51 -0000

On 2018-12-19 19:37, Venky Venkatesh wrote:
> 
> 
> On 12/18/18, 10:53 PM, "Mattias Rönnblom" <mattias.ronnblom@ericsson.com> wrote:
> 
>      On 2018-12-18 02:46, Venky Venkatesh wrote:
>      > Hi,
>      > I am relatively new to DPDK and am trying to use the eventdev library.
>      > The sw_evdev runs on a single core (service core). And then there is rte_event_eth_rx_adapter_ which links the sw_evdev to the ethdev. This adapter is also service core based. The DSW runs on all cores – and thus doesn’t use service cores. If we use the existing adapter, in the DSW paradigm:
>      >
>      >    *   The benefit of DSW is diminished as the packets would first have to go thru a possible choke point viz. the service core.
>      
>      Yes, but the practical implications may not be as great as you think. A
>      single service core will be able to handle (e.g. relay) a fair amount of
>      events into/out-of an event device.
>      
>      You are however not forced to use service cores. You may use one or more
>      of your workers to feed an event device.
> 
> [VV]: Just to be sure we are on the same page: The workers in a sort of alternating fashion call the ethdev to dequeue and enqueue_new into the eventdev and of course the dequeue from the eventdev (sort of analogous to the code that you provided with integrated producer and consumer).

Yes.