DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "sakaia@fujitsu.com" <sakaia@fujitsu.com>
Cc: "'users@dpdk.org'" <users@dpdk.org>
Subject: Re: Question about dpdk-pdump ring buffer
Date: Fri, 8 Apr 2022 08:11:55 -0700	[thread overview]
Message-ID: <20220408081155.6ff15aac@hermes.local> (raw)
In-Reply-To: <TYCPR01MB872413CA43110E0540B39349C7E99@TYCPR01MB8724.jpnprd01.prod.outlook.com>

On Fri, 8 Apr 2022 06:50:36 +0000
"sakaia@fujitsu.com" <sakaia@fujitsu.com> wrote:

> Question about dpdk-pdump ring buffer
> 
> With updating from 21.08 to 21.11, The packet capture is failed. 
> Previously(21.08) it works fine.
> 
> I want to know 2 things
> a)the difference of dpdk-pdump between 21.08 and 21.11 (seems bpf changes) 
> b)where pcap capture the ring buffer for secondary process?
> 
> The output is coming from print_pdump_stats function is zero for 3 parameters.(N.B.1) 
> Above parameters are counted on pdump_rxtx function.(it is zero on this function also) 
> The ring seems copied under mp_handle (process_msg) or mp_pdump.
> 
> P.S.
> I understand dpdk-pdump seems to be deprecated by introducing dpdk-dumpcap.
> 
> Reference
>   https://doc.dpdk.org/guides/prog_guide/pdump_lib.html
>   https://doc.dpdk.org/guides/prog_guide/multi_proc_support.html
> 
> N.B.1
> 
> ##### PDUMP DEBUG STATS #####
>  -packets dequeued:                     0
>  -packets transmitted to vdev:          0
>  -packets freed:                        0
> 
> Thanks in advance
> 
> Atsushi SAKAI

What is the application, is it built wit 21.11?

Note: You can't mix DPDK versions. The ring is internal structure so both application
and pdump must be built from same version.


      reply	other threads:[~2022-04-08 15:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08  6:50 sakaia
2022-04-08 15:11 ` 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=20220408081155.6ff15aac@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=sakaia@fujitsu.com \
    --cc=users@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).