From: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
To: Venky Venkatesh <vvenkatesh@paloaltonetworks.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Eventdev DSW and eth_rx_adapters
Date: Wed, 19 Dec 2018 21:02:48 +0100 [thread overview]
Message-ID: <f8f4a3da-cd25-d816-12d9-e7bbb3791912@ericsson.com> (raw)
In-Reply-To: <C287A243-DA6A-4D40-8D70-35FAE201F074@paloaltonetworks.com>
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.
prev parent reply other threads:[~2018-12-19 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 1:46 Venky Venkatesh
2018-12-19 6:52 ` Mattias Rönnblom
2018-12-19 18:37 ` Venky Venkatesh
2018-12-19 20:02 ` 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=f8f4a3da-cd25-d816-12d9-e7bbb3791912@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).