From: Stephen Hemminger <stephen@networkplumber.org>
To: ikuzar RABE <ikuzar9295@gmail.com>
Cc: users@dpdk.org
Subject: Re: multi-process support: how to share THE SAME packet between two different processes
Date: Fri, 25 Nov 2022 09:09:48 -0800 [thread overview]
Message-ID: <20221125090948.07295854@hermes.local> (raw)
In-Reply-To: <CACNnN_nNFGSPamGKh3FkhPpAZ2EqCzpd-W-fuJ=A70hjcr6aOQ@mail.gmail.com>
On Fri, 25 Nov 2022 17:27:46 +0100
ikuzar RABE <ikuzar9295@gmail.com> wrote:
> Hi all,
>
> I would like to know how do you usually proceed to retrieve and share the
> same packet read from NIC port between two different processes ? I try to
> work in zero-copy way.
>
> The first process job consists in parsing the packet and make some protocol
> statistics. The second one dumps the same packet into pcap file for further
> analysis with wireshark for example.
>
> I think none of the cases exposed here corresponds to my need: 43.
> Multi-process Support — Data Plane Development Kit 22.11.0-rc4
> documentation (dpdk.org)
> <https://doc.dpdk.org/guides/prog_guide/multi_proc_support.html#:~:text=Standalone%20DPDK%20processes%20are%20primary,process%20with%20same%20DPDK%20version.>.
> Am I wrong ?
>
> is there a dpdk-compliant way to do it with threads instead of processes ?
>
> Thank you for your help.
>
> Regards,
>
> ikuzar
Use a ring buffer.
Why are you reinventing what the pdump library does?
next prev parent reply other threads:[~2022-11-25 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 16:27 ikuzar RABE
2022-11-25 17:09 ` Stephen Hemminger [this message]
2022-11-28 14:10 ` ikuzar RABE
2022-11-28 17:16 ` Stephen Hemminger
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=20221125090948.07295854@hermes.local \
--to=stephen@networkplumber.org \
--cc=ikuzar9295@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).