DPDK usage discussions
 help / color / mirror / Atom feed
From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Lokesh Chakka <lvenkatakumarchakka@gmail.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: "Pathak, Pravin" <pravin.pathak@intel.com>,
	Bing Zhao <bingz@nvidia.com>,  users <users@dpdk.org>
Subject: Re: unable to capture packets
Date: Wed, 9 Oct 2024 13:27:17 +0000	[thread overview]
Message-ID: <PH8PR11MB6803B8CCA59A9C09EAB9774BD77F2@PH8PR11MB6803.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CACh--sjqgmFYiBix7WthsynhLeMkoo0O7A9wEkteGNoxJVCQrQ@mail.gmail.com>

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


> From: Lokesh Chakka <lvenkatakumarchakka@gmail.com>
> Sent: Wednesday, October 9, 2024 1:15 PM
> To: Stephen Hemminger <stephen@networkplumber.org>
> Cc: Pathak, Pravin <pravin.pathak@intel.com>; Bing Zhao <bingz@nvidia.com>; users <users@dpdk.org>
> Subject: Re: unable to capture packets
>
> hi,

Hi Chakka,

Please don't "top post" on mailing lists; a reply "inline" with context is a lot easier to follow for all current (and future!) readers.

> did certain modifications as per your suggestions. still the same problem. not able to capture any packets....!!!

Have you tried to run the DPDK example applications? Specifically, the skeleton/basicfwd.c has a "known good" setup routine,
and forwards packets on a single core. Perhaps it is a good place to compare your setup code to, as it its known working.

> I replaced 4096 with 512. rte_pktmbuf_pool_create is giving an error. for the time being i've left it as 4K only.
> I feel it should not be a problem.

There is a problem somewhere - and currently in your code it is not root caused. This is a time to re-check
code that "seemed ok" before, because somewhere something is not behaving as you expect.

> PFA for the revised code.

Attaching code to mailing lists is not an easy/good way to review; perhaps create a git repo and push the code there?

Then provide a link, and future patches could easily show what improvements/fixes occur. (If you email another
version of the "pmd.c" file, readers cannot know what changes were made -> leads to lots of duplication of review effort)


> Output is as follows :
>
> ==============================================================================================
> EAL: Detected CPU lcores: 40
> EAL: Detected NUMA nodes: 1
> EAL: Detected shared linkage of DPDK
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Selected IOVA mode 'VA'
> EAL: VFIO support initialized
> EAL: Using IOMMU type 1 (Type 1)
> ice_dev_init(): Failed to read device serial number
>
> ice_load_pkg_type(): Active package is: 1.3.39.0, ICE OS Default Package (double VLAN mode)
> main 53 port id: 0 num_of_pkts_per_queue: 4096
> ice_set_rx_function(): Using AVX2 Vector Rx (port 0).
> Received Interrupt Signal SIGINT (2). Exiting...
> main 98 time : 4 total pkts rcvd: 0 bandwidth: 0
> ==============================================================================================

<snip> previous conversation, as top-posted answers, and discussion was hard to follow.

It seems "num_of_pkts_per_queue" is used everywhere (mempool size, mbuf batch array size, rx_burst size, etc)
This is almost certainly impacting things somehow. Review skeleton/basicfwd.c for better sizes/values.

Hope that helps! Regards, -Harry



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

      reply	other threads:[~2024-10-09 13:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07 13:52 Lokesh Chakka
2024-10-07 15:21 ` Bing Zhao
2024-10-07 15:34   ` Stephen Hemminger
2024-10-07 15:36   ` Lokesh Chakka
2024-10-07 16:02     ` Pathak, Pravin
2024-10-07 22:10       ` Lokesh Chakka
2024-10-08  0:23         ` Stephen Hemminger
2024-10-09 12:15           ` Lokesh Chakka
2024-10-09 13:27             ` Van Haaren, Harry [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=PH8PR11MB6803B8CCA59A9C09EAB9774BD77F2@PH8PR11MB6803.namprd11.prod.outlook.com \
    --to=harry.van.haaren@intel.com \
    --cc=bingz@nvidia.com \
    --cc=lvenkatakumarchakka@gmail.com \
    --cc=pravin.pathak@intel.com \
    --cc=stephen@networkplumber.org \
    --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).