From: Venky Venkatesh <vvenkatesh@paloaltonetworks.com>
To: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DSW eventdev and multi-process DPDK
Date: Fri, 21 Dec 2018 18:34:00 +0000 [thread overview]
Message-ID: <8C05BF3C-5D90-4CD0-AA71-1B4C4324E53B@paloaltonetworks.com> (raw)
In-Reply-To: <e35340db-a364-4735-037d-c15220b3ecfe@ericsson.com>
On 12/21/18, 10:24 AM, "Mattias Rönnblom" <mattias.ronnblom@ericsson.com> wrote:
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.
[VV]: I don’t understand your last sentence. Suppose I am having multiple packet processing processes (each with a single thread and polling a disjoint set of queues) and each linked to DSW. Each process would invoke the enqueue which will be handled by the DSW linked to that process. Will the DSWs across these processes "collaborate" to get load balancing across the processes?
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.
next prev parent reply other threads:[~2018-12-21 18:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 5:13 Venky Venkatesh
2018-12-21 18:24 ` Mattias Rönnblom
2018-12-21 18:34 ` Venky Venkatesh [this message]
2018-12-21 18:59 ` Mattias Rönnblom
2018-12-21 19:12 ` Venky Venkatesh
2019-01-07 15:36 ` Mattias Rönnblom
2019-01-17 19:10 ` Venky Venkatesh
2019-01-18 6:36 ` Venky Venkatesh
2019-01-18 14:47 ` Mattias Rönnblom
2019-01-18 14:36 ` Mattias Rönnblom
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=8C05BF3C-5D90-4CD0-AA71-1B4C4324E53B@paloaltonetworks.com \
--to=vvenkatesh@paloaltonetworks.com \
--cc=dev@dpdk.org \
--cc=mattias.ronnblom@ericsson.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).