From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <users-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 4196AA0032
	for <public@inbox.dpdk.org>; Fri, 25 Nov 2022 18:09:52 +0100 (CET)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id B4D1F40156;
	Fri, 25 Nov 2022 18:09:51 +0100 (CET)
Received: from mail-pj1-f41.google.com (mail-pj1-f41.google.com
 [209.85.216.41]) by mails.dpdk.org (Postfix) with ESMTP id 3D48A40150
 for <users@dpdk.org>; Fri, 25 Nov 2022 18:09:50 +0100 (CET)
Received: by mail-pj1-f41.google.com with SMTP id
 u15-20020a17090a3fcf00b002191825cf02so351720pjm.2
 for <users@dpdk.org>; Fri, 25 Nov 2022 09:09:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=networkplumber-org.20210112.gappssmtp.com; s=20210112;
 h=content-transfer-encoding:mime-version:references:in-reply-to
 :message-id:subject:cc:to:from:date:from:to:cc:subject:date
 :message-id:reply-to;
 bh=dDO3rCMs20THnE4g3lmNM1hxblkq03y4bzaPrxIhNBA=;
 b=IN+ul7z4Uu3L178MEl6EEr4ktBRli3d5qC3lqaIWd0PwhewzwRnHY9PNEXadGXRWDN
 SXKGjNX/i/86lPUa/jbwz/7Kv4U8RnDs/xIwVrByKFFGXEQQweeGvqD9hRsTlWju/T1+
 ty/b22o8+rv/PK3zuqFpwXaMHCWEfquRqTmCPRw8YqJcMDfedf2+vT8CE1FNCDPOGkUJ
 dyVgCMR6MjH77eAm5xTLVt7FdZdEsOWtj29uitVsWTCn7R2M0hIdnlGZMs76VqsJQoE8
 x8l1FHVe2EDF2Qj/3YQD2//H6zCM3mgTfBvxefEvHNOkwzfW5YiL4iIl7Dvw0PndL9/A
 TfGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=content-transfer-encoding:mime-version:references:in-reply-to
 :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc
 :subject:date:message-id:reply-to;
 bh=dDO3rCMs20THnE4g3lmNM1hxblkq03y4bzaPrxIhNBA=;
 b=DVKQQBaqed55knxt+9Tbb1LMuDo7enUjayyK8mvoMctk3/6dtxdHEnYrxRTO2Zw6bu
 zBPVsfIvWjLLlAJwJs6OrMQmt+VRKMMzjWWr3Kh7ugAeSBiH32pCxY0o1R3HYjK/dbJq
 86LocjQOA4WAhJmJCHdDAuZE4KGV30xMYaN0AFxM9YtrcXOn1itxfULkRTKdcB2lYkoE
 udBAjPKDkTj8yDfGWh0v8j8YvwC1a+/3YGLtcnWVxHJueOxHihhMneEPtSs4Jzoq9IH/
 3ERzT1cEMgoVBMf1srbN3qvSGE4SW7BDlbHiQEjIHLWsHRThyYYeWOiFDuwkK4ATJqhq
 kV7A==
X-Gm-Message-State: ANoB5pkRIoy7qvIiteefuMmi/r75ftD4S2Y/JkdwjqWOMbwdD9Aremez
 hxiwqybDLaKLvb9sIFUnJCUWJw==
X-Google-Smtp-Source: AA0mqf6/8Ru6IghXJ2+4ExpyJIu0U/fBmQib5nHQXNPTms3LEtvym3G46QH649lCzPv0HUJoXmT6Rw==
X-Received: by 2002:a17:902:8604:b0:188:d78e:16ec with SMTP id
 f4-20020a170902860400b00188d78e16ecmr32352521plo.154.1669396188928; 
 Fri, 25 Nov 2022 09:09:48 -0800 (PST)
Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218])
 by smtp.gmail.com with ESMTPSA id
 a9-20020a1709027e4900b00188b63f0782sm1669958pln.288.2022.11.25.09.09.48
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Fri, 25 Nov 2022 09:09:48 -0800 (PST)
Date: Fri, 25 Nov 2022 09:09:48 -0800
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
Message-ID: <20221125090948.07295854@hermes.local>
In-Reply-To: <CACNnN_nNFGSPamGKh3FkhPpAZ2EqCzpd-W-fuJ=A70hjcr6aOQ@mail.gmail.com>
References: <CACNnN_nNFGSPamGKh3FkhPpAZ2EqCzpd-W-fuJ=A70hjcr6aOQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
Errors-To: users-bounces@dpdk.org

On Fri, 25 Nov 2022 17:27:46 +0100
ikuzar RABE <ikuzar9295@gmail.com> wrote:

> Hi all,
>=20
> 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.
>=20
> The first process job consists in parsing the packet and make some protoc=
ol
> statistics. The second one dumps the same packet into pcap file for furth=
er
> analysis with wireshark for example.
>=20
> I think none of the cases exposed here corresponds to my need: 43.
> Multi-process Support =E2=80=94 Data Plane Development Kit 22.11.0-rc4
> documentation (dpdk.org)
> <https://doc.dpdk.org/guides/prog_guide/multi_proc_support.html#:~:text=
=3DStandalone%20DPDK%20processes%20are%20primary,process%20with%20same%20DP=
DK%20version.>.
> Am I wrong ?
>=20
> is there a dpdk-compliant way to do it with threads instead of processes ?
>=20
> Thank you for your help.
>=20
> Regards,
>=20
> ikuzar

Use a ring buffer.
Why are you reinventing what the pdump library does?