DPDK usage discussions
 help / color / mirror / Atom feed
From: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: How to bind virtio interface in dpdk
Date: Wed, 7 Dec 2022 12:33:49 +0000	[thread overview]
Message-ID: <PSAPR04MB5516A7144411C13A8F66E70FD61A9@PSAPR04MB5516.apcprd04.prod.outlook.com> (raw)

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

Hi All,
   I am trying to bind virtio interface with my dpdk application.
Binding was successful but LINK create is failed in the log I am seeing
Port which was bound not probed in startup.
Please suggest how to bind the virtio interface into dpdk.

Steps I have tried to bind the port:

  1.  modprobe uio_pci_generic
  2.  dpdk-devbind.py -b uio_pci_generic  0000:02:00.0 0000:03:00.0
  3.  dpdk-devbind.py -s

Network devices using DPDK-compatible driver
0000:02:00.0 'Virtio network device 1041' drv=uio_pci_generic unused=virtio_pci,igb_uio,vfio-pci
0000:03:00.0 'Virtio network device 1041' drv=uio_pci_generic unused=virtio_pci,igb_uio,vfio-pci

Startup log:
IPv4 IP :
IPv6 IP : 0::0
EAL: Detected 24 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: No legacy callbacks, legacy socket not created
mempool MEMPOOL0 buffer 2304 pool 4096k cache 512 cpu 0
mempool MEMPOOL1 buffer 2304 pool 4096k cache 128 cpu 0
mempool MEMPOOL2 buffer 2304 pool 2048k cache 128 cpu 0

link LINK0 dev 0000:02:00.0 rxq 2 512 MEMPOOL0 txq 2 512 promiscuous on
Command "link" failed.


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

                 reply	other threads:[~2022-12-07 12:33 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PSAPR04MB5516A7144411C13A8F66E70FD61A9@PSAPR04MB5516.apcprd04.prod.outlook.com \
    --to=balakrishnan.k1@tatacommunications.com \
    --cc=users@dpdk.org \


* 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).