From: Denis Ovsienko <denis@ovsienko.info>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev <dev@dpdk.org>
Subject: Re: DPDK support in libpcap
Date: Sun, 2 Mar 2025 12:23:27 +0000 [thread overview]
Message-ID: <20250302122327.0e2173ad@atlas-11> (raw)
In-Reply-To: <CAOaVG14ZUZwNNkBGgD8phDnib7O6_cS476P2Z53dUnjTsxTLWQ@mail.gmail.com>
On Sat, 1 Mar 2025 10:28:21 +0100
Stephen Hemminger <stephen@networkplumber.org> wrote:
> Last time I looked at that code it was really ugly, and messy. But
> more of importantly it was the wrong use case. Very few users will
> want to have a NIC dedicated to capture only.
>
> The whole thing should be rewritten so that tcpdump/ Wireshark can
> run as secondary process using existing pdump API.
Thank you for looking Stephen.
In case there is a volunteer to fix this at some time, this could be a
useful starting point for them. You are welcome to update the bug
report [1] if you think this would help.
1: https://github.com/the-tcpdump-group/libpcap/issues/1159
--
Denis Ovsienko
prev parent reply other threads:[~2025-03-02 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 14:20 Denis Ovsienko
2025-03-01 9:28 ` Stephen Hemminger
2025-03-02 12:23 ` Denis Ovsienko [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=20250302122327.0e2173ad@atlas-11 \
--to=denis@ovsienko.info \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).