DPDK patches and discussions
 help / color / mirror / Atom feed
From: Anjali Kulkarni <anjali@juniper.net>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Question on using SR-IOV with dpdk apps
Date: Mon, 4 Aug 2014 19:43:55 +0000	[thread overview]
Message-ID: <D0052E56.2D38F%anjali@juniper.net> (raw)

Hi,

I am using SR-IOV and pass through to run a DPDK app. I am running it on
host. SR-IOV should split the NIC into multiple Vfs. I have split each NIC
into 2 Vfs. However, when I run the DPDK app, I get error initializing the
port no.2 of DPDK.
I am running the app with these options:
--rx "(0,0,0,1),(1,0,2,1), (2,0,3,1), (3,0,4,1)" --tx "(0,1), (1,1),
(2,1), (3,1)"

This is for 2 physical NICs, each having 2 Vfs. The error I get is:

Initializing NIC port 0 ...                                    |
|RPIOIF DETACHED   
|Initializing NIC port 0 RX queue 0 ...                         |
|                  
|Initializing NIC port 0 TX queue 0 ...                         |
|HOSTIF DETACHED   
|Initializing NIC port 1 ...                                    |
|                  
|Initializing NIC port 1 RX queue 0 ...                         |
|                  
|Initializing NIC port 1 TX queue 0 ...                         |
|                  
|Initializing NIC port 2 ...                                    |
|                  
|PANIC in app_init_nics():                                      |
|                  
|Cannot init NIC port 2 (-22)


Can someone pls clarify how DPDK views it's port nos, i.e. Scans the
devices and sees each nic? I see 4 /dev/uioX devices. I assume it scans
for these igb_uio devices. These are present. Then why can it not detect
the other 2 NICs?

Thanks
Anjali

             reply	other threads:[~2014-08-04 19:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 19:43 Anjali Kulkarni [this message]
2014-08-04 19:44 ` Anjali Kulkarni
2014-08-04 19:53   ` Richardson, Bruce
2014-08-04 20:24     ` Anjali Kulkarni
2014-08-04 20:26 Anjali Kulkarni
2014-08-05 14:38 ` Patrick McGleenon
2014-08-05 15:09   ` Xie, Huawei

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=D0052E56.2D38F%anjali@juniper.net \
    --to=anjali@juniper.net \
    --cc=dev@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).