From: Puneet Singh <singh1989p@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Regarding usage of vmxnet3 PMD with DPDK2.0
Date: Thu, 25 Jun 2015 10:24:27 +0530 [thread overview]
Message-ID: <CAEPmXpjZsNZy4Uyz6P+hozA0WkaKh9vtR9B4FoFpWyAXBhNcSQ@mail.gmail.com> (raw)
I am migrating from using DPDK1.6r2 and the external vmxnet3 user map
driver to DPDK2.0.
I believe with DPDK2.0, the vmxnet3 PMD is builtin and I don’t need to
use the external driver.
I have been able to build the DPDK2.0 and I see that
CONFIG_RTE_LIBRTE_VMXNET3_PMD is set to y in the config.
Question is, what should be the steps that I follow on the ESXi node
in my virtual machine to detect the NIC with the above driver (I do
have vmxnet3 NIC there)
Should I load the uio and take over the NIC the usual way with igb_uio
and then run my application or are there any other steps to be
followed.
Regards
-Puneet
next reply other threads:[~2015-06-25 4:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 4:54 Puneet Singh [this message]
2015-06-25 6:00 ` Patel, Rashmin N
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=CAEPmXpjZsNZy4Uyz6P+hozA0WkaKh9vtR9B4FoFpWyAXBhNcSQ@mail.gmail.com \
--to=singh1989p@gmail.com \
--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).