DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Patel, Rashmin N" <rashmin.n.patel@intel.com>
To: Karmarkar Suyash <skarmarkar@sonusnet.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK 1.6 and Cisco VIC-NIC pmd fails to initialize with VMWare ESX 5.5
Date: Thu, 19 Nov 2015 18:19:45 +0000	[thread overview]
Message-ID: <C68F1134885B32458704E1E4DA3E34F34279107E@FMSMSX105.amr.corp.intel.com> (raw)
In-Reply-To: <BY1PR03MB1338A57773D5EAAE8BBAD00DB31B0@BY1PR03MB1338.namprd03.prod.outlook.com>

What is the error code it failed with?

There is no dependency between ESXi and DPDK versions as such. But depending your VM settings, it may pop up some issues related to memory assigned to VM.

When you use NIC in Hypervisor and feed packets to VM via Vmxnet3, the guest OS can use Vmxnet3-pmd and that's the sole requirement. Guest OS or DPDK API in VM are unaware and independent of the physical NIC beneath.
When you use NIC in VM via Passthrough (or device direct assignment,) the guest OS can use ixgbe-pmd/igb-pmd/xyz-pmd to control them for Rx/Tx operations. ESXi can't look into such device operations like it can't see packets coming in or going out.
When you enable SRIOV on a NIC, you get a PF and multiple VFs and if you use a NIC-Virtual Function via passthrough, the guest OS can use respective pmd (ixgbevf/igbvf/xyzvf) in DPDK API to control it for Rx/Tx ops. ESXi control the Physical Function through a respective driver (ixgbe/igb/xyz provided with ESXi) DPDK API doesn't have support to run in ESXi to control that PF.

Thanks,
Rashmin

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Karmarkar Suyash
Sent: Wednesday, November 18, 2015 8:34 PM
To: dev@dpdk.org
Subject: [dpdk-dev] DPDK 1.6 and Cisco VIC-NIC pmd fails to initialize with VMWare ESX 5.5

Hello All,

I am trying some experiments with DPDK 1.6 and Cisco NIC - (0000:06:00.0 Network controller: Cisco Systems Inc. Cisco VIC Ethernet NIC [vmnic0]), on the guest I am using VMXNET3 as interface/pmd and one weird behavior that is see is with VMWare ESX 5.5 DPDK is not able to initialize the NIC and I get the error rte_eth_dev_start failed with error code as, but same NIC and with DPDK 1.6 version works fine with VMWare ESX 6.0 and with VMXNET3 PMD.

Two questions:

1.     Is there any dependency with VMWare version ESX (5.0/5.1/6.0) with DPDK Release version (1.6/1.7/2.x)? If yes can you please let me know?

2.     If we are not using the NIC in pass-through mode and we are using it via Hypervisor - vmxnet3 or virtio pmd is there still a dependency for the list of NIC's supported by DPDK?

Regards
Suyash

  reply	other threads:[~2015-11-19 18:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19  3:33 Karmarkar Suyash
2015-11-19 18:19 ` Patel, Rashmin N [this message]
2015-11-19 18:36   ` Karmarkar Suyash
2015-11-19  5:46 Karmarkar Suyash

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=C68F1134885B32458704E1E4DA3E34F34279107E@FMSMSX105.amr.corp.intel.com \
    --to=rashmin.n.patel@intel.com \
    --cc=dev@dpdk.org \
    --cc=skarmarkar@sonusnet.com \
    /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).