DPDK usage discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: FRANCISCO ARNALDO BOIX MARTINEZ <franciscoarnaldo.boixm@um.es>
Cc: "users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: error: No probed ethernet devices
Date: Thu, 3 Aug 2023 09:06:22 +0100	[thread overview]
Message-ID: <ZMtf/r8l39HSocXP@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <PAXPR08MB681451E6ABE8FE9AE653BDE5900BA@PAXPR08MB6814.eurprd08.prod.outlook.com>

On Wed, Aug 02, 2023 at 01:29:03PM +0000, FRANCISCO ARNALDO BOIX MARTINEZ wrote:
>    Hi team,
> 
>    I am trying to run dpdk-testpmd utility, but I am not able to make it
>    work even though I have already used dpdk-devbind.py utility. I haven't
>    been able to find the solution yet, could you please help me?
> 
>    I get the following output while executing ./usertools/dpdk-devbind.py
>    -s:
> 
>    Network devices using kernel driver
>    ===================================
>    0000:04:00.0 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
>    8168' if=enp4s0 drv=r8169 unused=vfio-pci *Active*

This indicates that you have only a single network card port, which is
bound to the kernel for kernel use. It's also a device which I don't
believe we have drivers for in DPDK - so even if you did unbind it (and
lose network connectivity to your board - it still likely wouldn't be
usable with DPDK.

I therefore think you need to add some supported network devices to your
system to use DPDK. You generally need to keep one network port for kernel
use and use DPDK on the rest. The only exception is if you plan on using
DPDK through af_xdp or af_packet or similar driver that takes packets from
a kernel-connected port.

Regards,
/Bruce

      reply	other threads:[~2023-08-03  8:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 13:29 FRANCISCO ARNALDO BOIX MARTINEZ
2023-08-03  8:06 ` Bruce Richardson [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=ZMtf/r8l39HSocXP@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=franciscoarnaldo.boixm@um.es \
    --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).