DPDK usage discussions
 help / color / mirror / Atom feed
From: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: RE: how to run dpdk app with valgrind
Date: Wed, 6 Jul 2022 06:00:35 +0000	[thread overview]
Message-ID: <PSAPR04MB551631B5E53B52DBBE91289ED6809@PSAPR04MB5516.apcprd04.prod.outlook.com> (raw)
In-Reply-To: <20220705090412.5385dae2@hermes.local>

Hi Stephen,
    Please find the response below.
What architecture (x86)?

Architecture is x86.
 
What DPDK version?

DPDK version 20.11

 What version of valgrind?
valgrind-3.19.0

Are you using VFIO, igb_uio or other method of hardware access?

Igbuio

Regards,
Bala 


-----Original Message-----
From: Stephen Hemminger <stephen@networkplumber.org> 
Sent: 05 July 2022 21:34
To: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>
Cc: users@dpdk.org
Subject: Re: how to run dpdk app with valgrind

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

On Tue, 5 Jul 2022 11:10:37 +0000
Balakrishnan K <Balakrishnan.K1@tatacommunications.com> wrote:

> Hi All,
>     Is there any documents available to run the dpdk application with valgrind.
> I am trying to run our application with dpdk getting warning and the process is not starting up.
>
>
> IPv4 IP : 1.1.1.1
> IPv6 IP : 0::0
> EAL: Detected 80 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Selected IOVA mode 'PA'
> EAL: Probing VFIO support...
> EAL: WARNING! Base virtual address hint (0xa80001000 != 0x1040000000) not respected!
> EAL:    This may cause issues with mapping memory into secondary processes
>
> Could you please help on this?
>
> Regards,
> Bala

What architecture (x86)? What DPDK version? What version of valgrind?
Are you using VFIO, igb_uio or other method of hardware access?

Valgrind works for us on Arm64 and VFIO.

  reply	other threads:[~2022-07-06  6:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 11:10 Balakrishnan K
2022-07-05 13:22 ` Pathak, Pravin
2022-07-06  5:54   ` Balakrishnan K
2022-07-06 11:45     ` Pathak, Pravin
2022-07-06 12:04       ` Balakrishnan K
2022-07-05 16:04 ` Stephen Hemminger
2022-07-06  6:00   ` Balakrishnan K [this message]
2022-07-06  7:11     ` Balakrishnan K

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=PSAPR04MB551631B5E53B52DBBE91289ED6809@PSAPR04MB5516.apcprd04.prod.outlook.com \
    --to=balakrishnan.k1@tatacommunications.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).