From: Bhavesh Davda <bhavesh@vmware.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Henry Wang <wang_hr@neusoft.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0
Date: Fri, 10 May 2013 09:21:36 -0700 (PDT) [thread overview]
Message-ID: <525534677.5312512.1368202896189.JavaMail.root@vmware.com> (raw)
In-Reply-To: <20130510091549.3c064df6@nehalam.linuxnetplumber.net>
Right: VMware has supported VMDirectPath passthrough since ESXi 4.0, on any platform with an IOMMU (Intel VT-d) which is anything Nehalem Xeons or newer.
I know this is a DPDK forum, but Stephen, if you know of specific limitations of ESXi 5.1's SR-IOV support, please let me know and I'll make sure we work on addressing them.
--
Bhavesh Davda
----- Original Message -----
> From: "Stephen Hemminger" <stephen@networkplumber.org>
> To: "Bhavesh Davda" <bhavesh@vmware.com>
> Cc: "Henry Wang" <wang_hr@neusoft.com>, dev@dpdk.org
> Sent: Friday, May 10, 2013 9:15:49 AM
> Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0
>
> On Fri, 10 May 2013 09:05:08 -0700 (PDT)
> Bhavesh Davda <bhavesh@vmware.com> wrote:
>
> > ESXi 5.0 doesn't have SR-IOV support (it's in the code, but is disabled and
> > not usable for customers). VMware introduced SR-IOV support, including out
> > of the box support for Intel Niantic 10GbE NICs, in ESXi 5.1.
> >
>
> You can use PCI passthrough (Directpath) on 5.0 (and 5.1).
> I found that SR-IOV on Vmware is even more fussy than SR-IOV on Linux.
> It requires a supported platform with VT-d and PCIe ASPM
>
next prev parent reply other threads:[~2013-05-10 16:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 1:00 Rui Vaz (ruvaz)
2013-05-10 1:18 ` Henry Wang
2013-05-10 16:05 ` Bhavesh Davda
2013-05-10 16:15 ` Stephen Hemminger
2013-05-10 16:21 ` Bhavesh Davda [this message]
2013-05-10 18:44 ` Stephen Hemminger
2013-05-10 19:10 ` Bhavesh Davda
2013-05-10 19:29 ` Stephen Hemminger
2013-05-10 21:00 ` Bhavesh Davda
2013-05-18 0:09 ` Rui Vaz (ruvaz)
2013-05-10 15:47 ` Vincent JARDIN
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=525534677.5312512.1368202896189.JavaMail.root@vmware.com \
--to=bhavesh@vmware.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=wang_hr@neusoft.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).