From: Stephen Hemminger <stephen@networkplumber.org>
To: Marat Khalili <qm2k21@gmail.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Reshma Pattan <reshma.pattan@intel.com>,
dev@dpdk.org
Subject: Re: [PATCH v3] examples/rpcapd: demo version of packet capture daemon
Date: Mon, 28 Sep 2026 10:24:29 -0700 [thread overview]
Message-ID: <20260928102429.70ca1040@phoenix.local> (raw)
In-Reply-To: <2ec5b83b-54b7-4b69-afbd-33d4e4e81967@gmail.com>
On Mon, 28 Sep 2026 17:18:40 +0100
Marat Khalili <qm2k21@gmail.com> wrote:
> Summarizing the exchange to v2, our own copy of rpcap-protocol.h is
> unavoidable here since one included in libpcap is an internal header
> that is not installed by design (irrespective of package maintainers). I
> am ready to ack the patch after this is clarified in the code to prevent
> other people from being similarly confused since situation with the
> dependencies here is quite complex.
>
> My request to better mark sections of main.c responsible for different
> concerns still stands, but is not a show stopper. Same for my request to
> make it a part of dpdk-testpmd instead of a secondary process. Anyone
> interested can probably do either or both locally in half an hour in a
> code agent anyway.
>
I have a new version which has more features and splits up the code.
next prev parent reply other threads:[~2026-09-28 17:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 21:07 [PATCH] examples/rpcapd: demo version of packet capture daemon Stephen Hemminger
2026-09-20 18:59 ` [PATCH v2] " Stephen Hemminger
2026-09-21 9:51 ` Marat Khalili
2026-09-21 15:57 ` Stephen Hemminger
2026-09-21 15:58 ` Stephen Hemminger
2026-09-21 16:43 ` Marat Khalili
2026-09-21 17:31 ` Stephen Hemminger
2026-09-21 17:53 ` Marat Khalili
2026-09-21 16:17 ` Stephen Hemminger
2026-09-22 18:45 ` Stephen Hemminger
2026-09-22 21:31 ` [PATCH v3] " Stephen Hemminger
2026-09-28 16:18 ` Marat Khalili
2026-09-28 17:24 ` Stephen Hemminger [this message]
2026-10-01 2:35 ` [PATCH v4 0/4] add rpcap remote " Stephen Hemminger
2026-10-01 2:35 ` [PATCH v4 1/4] pcapng: add API to read back capture mbuf header Stephen Hemminger
2026-10-01 2:35 ` [PATCH v4 2/4] app/rpcapd: remote pcap daemon Stephen Hemminger
2026-10-01 18:50 ` Marat Khalili
2026-10-01 2:35 ` [PATCH v4 3/4] app/rpcapd: add TLS support Stephen Hemminger
2026-10-01 2:35 ` [PATCH v4 4/4] app/rpcapd: add host list option Stephen Hemminger
2026-10-01 18:50 ` [PATCH v4 0/4] add rpcap remote capture daemon Marat Khalili
2026-10-01 23:00 ` 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=20260928102429.70ca1040@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=qm2k21@gmail.com \
--cc=reshma.pattan@intel.com \
--cc=thomas@monjalon.net \
/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