From: "Hunt, David" <david.hunt@intel.com>
To: Jean-Philippe ANDRIOT <jp.andriot@gmail.com>, users@dpdk.org
Subject: Re: [dpdk-users] Is it possible to use distributor library in multi-process mode ?
Date: Tue, 13 Jun 2017 16:35:05 +0100 [thread overview]
Message-ID: <99d5092a-aaa9-d526-118f-4441681d20a0@intel.com> (raw)
In-Reply-To: <12e40f2e-6bd3-1443-9895-0dd75e82a769@gmail.com>
On 9/6/2017 9:17 PM, Jean-Philippe ANDRIOT wrote:
>
> Hi,
>
> I would like to use packet distributor library in multi-process mode,
> meaning both distributor core and every worker are running in a
> different process (secondary proc type).
>
> However, there is no /rte_distributor_lookup/ function to get a
> distributor instance from a DPDK secondary process, such as
> /rte_ring_lookup/ for rings.
>
> I had a look to the implementation of both ring and distributor and it
> looks like both are created the same way (rte_memzone allocation and
> registration in a RTE_TAILQ in shm).
>
> So I'm wondering if the rte_distributor_lookup function could be
> easily implemented ( based on rte_ring_lookup ) or if there are
> specific issues which prevent distributor to be used in multi process
> mode.
>
> Thanks !
>
Jean-Philippe,
It sounds like you're going in the right direction for this. I
haven't attempted a multi-process implementation myself, but what you're
describing is theoretically possible.
If you implemented an rte_distributor_lookup function, once you get the
rte_distributor instance, you should then be able to call the client
API's to get and return packets to the distributor app.
Please ensure that the number of running workers matches the number of
workers in the created distributor instance, and that each app passes in
a unique worker_id.
Regards,
Dave.
prev parent reply other threads:[~2017-06-13 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANcaouVt+8RN6RPajonSYY9Rn2V10kWN2H4XkPiieYiQvosiTQ@mail.gmail.com>
2017-06-09 20:17 ` Jean-Philippe ANDRIOT
2017-06-13 15:35 ` Hunt, David [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=99d5092a-aaa9-d526-118f-4441681d20a0@intel.com \
--to=david.hunt@intel.com \
--cc=jp.andriot@gmail.com \
--cc=users@dpdk.org \
/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).