<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
Hey Thomas,</div>
<div style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
In DPDK test cases, I agree that nothing other than Ethernet link types are currently used. However, when using DPDK Rawdev, the protocol is not usually Ethernet. In my case, I am trying to create PCAP files based on custom PCI-e traffic. The DPDK pcapng library
currently hardcodes the metadata to be Ethernet, which cannot be read properly by Wireshark. Allowing the user to specify the protocol link type, the user can ensure the pcapng metadata matches the traffic data.</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
Dylan</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Thomas Monjalon <thomas@monjalon.net><br>
<b>Sent:</b> Saturday, September 27, 2025 3:28 AM<br>
<b>To:</b> Dylan Schneider <schneide@qti.qualcomm.com><br>
<b>Cc:</b> dev@dpdk.org <dev@dpdk.org>; Reshma Pattan <reshma.pattan@intel.com>; Jerin Jacob <jerinj@marvell.com>; Kiran Kumar K <kirankumark@marvell.com>; Nithin Dabilpuram <ndabilpuram@marvell.com>; Zhirun Yan <yanzhirun_163@163.com>; Stephen Hemminger <stephen@networkplumber.org><br>
<b>Subject:</b> Re: [PATCH v2] pcapng: allow any protocol link type for the interface block</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.<br>
<br>
26/09/2025 02:04, Stephen Hemminger:<br>
> On Wed, 27 Aug 2025 16:32:15 -0600<br>
> Schneide <schneide@qti.qualcomm.com> wrote:<br>
><br>
> ><br>
> > +* pcapng: Changed the API for adding interfaces to include a link type argument.<br>
> > + The link type was previously hardcoded to the ethernet link type in the API.<br>
> > + This argument is added to ``rte_pcapng_add_interface``.<br>
> > + These functions are versioned to retain binary compatibility until the next LTS release.<br>
><br>
> Since link connector is now merged, and that wording might overlap and<br>
> be confusing. Would be could to add reference to pcap-linktype.7 man<br>
> page.<br>
<br>
I'm not sure it overlaps.<br>
RTE_ETH_LINK_CONNECTOR is about Ethernet cables while<br>
pcap link type will be simply Ethernet type.<br>
<br>
This being said, I don't understand the immediate benefit of this commit.<br>
Why pcap link type would not be always Ethernet in DPDK case?<br>
I think the only benefit is for future if other link types are added.<br>
Is there something else I'm missing?<br>
<br>
<br>
</div>
</span></font></div>
</body>
</html>