From: Stephen Hemminger <stephen@networkplumber.org>
To: "Dey, Souvik" <sodey@sonusnet.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Vmxnet3 activation of device fails in DPDK1.7
Date: Thu, 10 Dec 2015 09:24:19 -0800 [thread overview]
Message-ID: <20151210092419.5a960ad3@xeon-e3> (raw)
In-Reply-To: <BN3PR0301MB120201E64FA67DEE11329DE9DAE90@BN3PR0301MB1202.namprd03.prod.outlook.com>
On Thu, 10 Dec 2015 10:22:30 +0000
"Dey, Souvik" <sodey@sonusnet.com> wrote:
> Hi,
> In DPDK 1.7 , while using the vmxnet3 pmd on vmware Esxi 5.5 update 3 we are seeing that activation of the device fails.
Please try something more recent. DPDK 1.7 had a version of vmxnet3
which was brand new at the time, and had lots of bugs. A lot of collabrative
changes went into later versions. I would recommend 2.0 or later
if possible.
next prev parent reply other threads:[~2015-12-10 18:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 10:22 Vmxnet3 activation of device fails in DPDK1.7 Dey, Souvik
2015-12-10 17:24 ` Stephen Hemminger [this message]
2015-12-14 4:52 ` Dey, Souvik
-- strict thread matches above, loose matches on Subject: below --
2015-12-10 18:36 Yong Wang
2015-12-14 5:01 ` Dey, Souvik
2015-12-14 6:27 ` Yong Wang
2015-12-14 7:06 ` Dey, Souvik
2015-12-22 20:36 ` Yong Wang
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=20151210092419.5a960ad3@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=sodey@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.