DPDK usage discussions
 help / color / mirror / Atom feed
From: Anna Tauzzi <admin@argonnetech.net>
To: users@dpdk.org
Subject: rte_dev_probe on secondary succeeds but I get some strange printouts
Date: Mon, 29 Aug 2022 16:43:44 +0200	[thread overview]
Message-ID: <CAK_0FMQVb5DD72k6VfhuxgNjy6gD1gneV1XoeoOGLzhcpuPYcw@mail.gmail.com> (raw)

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

I have a program that, when launched as primary, spawns a secondary.

If I issue an rte_dev_probe in the primary it works properly while if I
issue the rte_dev_probe in the secondary, it returns no error but I get
some strange printouts. Please notice that I launch the primary with option
--allow '0000:00:00.0' and the offending printouts are:

iavf_execute_vf_cmd(): No response for cmd 26
iavf_execute_vf_cmd(): No response for cmd 26
iavf_set_hena(): Failed to execute command of OP_SET_RSS_HENA
iavf_default_rss_disable(): fail to disable default RSS,lack PF support

Complete log:
sudo build/simple_eth_mp -l 30-34 --allow '0000:00:00.0'
--- PRIMARY ---
EAL: Detected CPU lcores: 56
EAL: Detected NUMA nodes: 2
EAL: Detected shared linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: 2048 hugepages of size 2097152 reserved, but no mounted hugetlbfs
found for that size
EAL: VFIO support initialized
TELEMETRY: No legacy callbacks, legacy socket not created
APP: Finished Process Init.
Num ports pri 0
Starting core on primary lcore 31
Starting core on primary lcore 32
Starting core on primary lcore 33
Starting core on primary lcore 34
EAL: Detected CPU lcores: 56
EAL: Detected NUMA nodes: 2
EAL: Auto-detected process type: SECONDARY
EAL: Detected shared linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_3658_1f2b30323f21e
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
EAL: 0000:86:02.0 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:86:02.0 cannot be used
EAL: 0000:86:02.1 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:86:02.1 cannot be used
EAL: 0000:86:02.2 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:86:02.2 cannot be used
EAL: 0000:86:02.3 cannot find TAILQ entry for PCI device!
EAL: Requested device 0000:86:02.3 cannot be used

--- SECONDARY ---
NUM PORTS AVAILABLE on SEC: 0
GOING TO PROBE VF INTERFACE 0000:86:02.0 on Ethernet X710/X557-AT 10GBASE-T
EAL: Using IOMMU type 1 (Type 1)
EAL: Probe PCI driver: net_iavf (8086:154c) device: 0000:86:02.0 (socket 1)
iavf_execute_vf_cmd(): No response for cmd 26
iavf_set_hena(): Failed to execute command of OP_SET_RSS_HENA
iavf_default_rss_disable(): fail to disable default RSS,lack PF support
EAL: Using IOMMU type 1 (Type 1)
EAL: Probe PCI driver: net_iavf (8086:154c) device: 0000:86:02.0 (socket 1)
iavf_handle_virtchnl_msg(): command mismatch, expect 0, get 26
NUM PORTS AVAILABLE on SEC: 1
Starting core on secondary 6
Starting core on secondary 7
Starting core on secondary 8
Starting core on secondary 9
Starting core on secondary 10
Secondary started


Regards,
Anna

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

                 reply	other threads:[~2022-08-29 14:43 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=CAK_0FMQVb5DD72k6VfhuxgNjy6gD1gneV1XoeoOGLzhcpuPYcw@mail.gmail.com \
    --to=admin@argonnetech.net \
    --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).