[dpdk-dev] Eventdev DSW and eth_rx_adapters

Mattias Rönnblom mattias.ronnblom at ericsson.com
Wed Dec 19 21:02:48 CET 2018

On 2018-12-19 19:37, Venky Venkatesh wrote:
> On 12/18/18, 10:53 PM, "Mattias Rönnblom" <mattias.ronnblom at 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).


More information about the dev mailing list