DPDK usage discussions
 help / color / mirror / Atom feed
From: David Aldrich <david.aldrich.ntml@gmail.com>
To: users <users@dpdk.org>
Subject: Help needed with hugepages and binding ports
Date: Thu, 29 Aug 2024 16:01:06 +0100	[thread overview]
Message-ID: <CAJK_iegAJDNjYkF5CRkH0zW-szCxpM6m6qv+FG9jC=0TDeybWg@mail.gmail.com> (raw)

Hi,

We are running DPDK v.19.11.14 on Ubuntu 22.04 LTS. Our goal is to use
DPDK to accelerate UDP communication on a Broadcom 57504 network
controller.

I have some problems with hugepages and binding of ports and would be
grateful for some help please.

1) Firstly, regarding hugepages, our kernel cmdline includes:

default_hugepagesz=1G hugepagesz=1G hugepages=25 hugepagesz=2M hugepages=1024

After reboot I see:

$ cat /proc/meminfo | grep Hugepages

Hugepagesize:    1048576 kB

This is no mention of 2MB pages. Is that expected?

I call rte_eal_init() with parameter:

-m 4000

but see:

EAL: 1024 hugepages of size 2097152 reserved, but no mounted hugetlbfs
found for that size

Is that a problem?

2) Secondly, I use dpdk-devbind.py to bind the first device of the
57504 controller to DPDK. dpdk-devbind.py reports:

Network devices using DPDK-compatible driver
============================================
0000:43:00.0 'BCM57504 NetXtreme-E 10Gb/25Gb/40Gb/50Gb/100Gb/200Gb
Ethernet 1751' drv=igb_uio unused=bnxt_en,vfio-pci

but when our application calls rte_eth_dev_count_avail() the return
value is 0 and so the application reports:

ERROR: EXIT_FAILURE : No DPDK ports found - have you run the DPDK setup script?

Any idea why the bound port is not found?

3) Finally, our setup script inserts modules igb_uio.ko and
rte_kni.ko. Is this adequate for the Broadcom BCM57504?

Best regards
David

                 reply	other threads:[~2024-08-29 15:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAJK_iegAJDNjYkF5CRkH0zW-szCxpM6m6qv+FG9jC=0TDeybWg@mail.gmail.com' \
    --to=david.aldrich.ntml@gmail.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).