DPDK usage discussions
 help / color / mirror / Atom feed
From: ikuzar RABE <ikuzar9295@gmail.com>
To: stephen@networkplumber.org
Cc: users@dpdk.org
Subject: Re: multi-process support: how to share THE SAME packet between two different processes
Date: Mon, 28 Nov 2022 15:10:39 +0100	[thread overview]
Message-ID: <CACNnN_kx3Fq9mfzP4BncgxZci5YH-rKftMuhYR8kstacjrkB9w@mail.gmail.com> (raw)
In-Reply-To: <20221125090948.07295854@hermes.local>

[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]

In this case:  9. DPDK packet capture libraries and tools — Data Plane
Development Kit 22.11.0 documentation
<https://doc.dpdk.org/guides/howto/packet_capture_framework.html>, which
process is responsible of deallocing the memory occupied by a packet ? the
primary process or the dpdk-dumpcap tool process ?
if one process deallocates a memory, the second one will point to nothing...

ikuzar

i

Le ven. 25 nov. 2022 à 18:09, Stephen Hemminger <stephen@networkplumber.org>
a écrit :

> 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?
>

[-- Attachment #2: Type: text/html, Size: 2420 bytes --]

  reply	other threads:[~2022-11-28 14:10 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
2022-11-28 14:10   ` ikuzar RABE [this message]
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=CACNnN_kx3Fq9mfzP4BncgxZci5YH-rKftMuhYR8kstacjrkB9w@mail.gmail.com \
    --to=ikuzar9295@gmail.com \
    --cc=stephen@networkplumber.org \
    --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).