DPDK patches and discussions
 help / color / mirror / Atom feed
* DPDK support in libpcap
@ 2025-02-28 14:20 Denis Ovsienko
  2025-03-01  9:28 ` Stephen Hemminger
  0 siblings, 1 reply; 3+ messages in thread
From: Denis Ovsienko @ 2025-02-28 14:20 UTC (permalink / raw)
  To: dev

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: DPDK support in libpcap
  2025-02-28 14:20 DPDK support in libpcap Denis Ovsienko
@ 2025-03-01  9:28 ` Stephen Hemminger
  2025-03-02 12:23   ` Denis Ovsienko
  0 siblings, 1 reply; 3+ messages in thread
From: Stephen Hemminger @ 2025-03-01  9:28 UTC (permalink / raw)
  To: Denis Ovsienko; +Cc: dev

[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: DPDK support in libpcap
  2025-03-01  9:28 ` Stephen Hemminger
@ 2025-03-02 12:23   ` Denis Ovsienko
  0 siblings, 0 replies; 3+ messages in thread
From: Denis Ovsienko @ 2025-03-02 12:23 UTC (permalink / raw)
  To: Stephen Hemminger; +Cc: dev

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-03-02 12:23 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-02-28 14:20 DPDK support in libpcap Denis Ovsienko
2025-03-01  9:28 ` Stephen Hemminger
2025-03-02 12:23   ` Denis Ovsienko

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).