DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Denis Ovsienko <denis@ovsienko.info>
Cc: dev <dev@dpdk.org>
Subject: Re: DPDK support in libpcap
Date: Sat, 1 Mar 2025 10:28:21 +0100	[thread overview]
Message-ID: <CAOaVG14ZUZwNNkBGgD8phDnib7O6_cS476P2Z53dUnjTsxTLWQ@mail.gmail.com> (raw)
In-Reply-To: <20250228142005.1052bd2d@atlas-11>

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

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.

On Fri, Feb 28, 2025, 15:20 Denis Ovsienko <denis@ovsienko.info> wrote:

> Hello all.
>
> libpcap has been implementing DPDK packet capture support for some
> time, in that a contributor added this support using DPDK 18.11.  This
> code stopped working with later versions of DPDK and still remains
> broken.
>
> Would anybody be interested to upgrade pcap-dpdk.c in libpcap to the
> latest stable release of DPDK, to confirm whether it works as intended
> and maybe even to keep this module better maintained in future?
>
> --
>     Denis Ovsienko
>

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

      reply	other threads:[~2025-03-01  9:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 14:20 Denis Ovsienko
2025-03-01  9:28 ` Stephen Hemminger [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=CAOaVG14ZUZwNNkBGgD8phDnib7O6_cS476P2Z53dUnjTsxTLWQ@mail.gmail.com \
    --to=stephen@networkplumber.org \
    --cc=denis@ovsienko.info \
    --cc=dev@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).