From: Yong Wang <yongwang@vmware.com>
To: Bin Zhang <bzhang@varmour.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] vmxnet3 can not active device in 5.5
Date: Sat, 31 Oct 2015 09:11:07 +0000 [thread overview]
Message-ID: <D1BB1E46-96E0-43C6-9D54-476016B79ED7@vmware.com> (raw)
In-Reply-To: <CAJ-NKLrZfPzsmO-S1Sn=fCDkdT3rXJ1WUxU6HnBsHCDnGRq-8w@mail.gmail.com>
On 10/22/15, 8:54 PM, "Bin Zhang" <bzhang@varmour.com> wrote:
>Hi,
>
>I got this issue in recent update esxi 5.5
Can you share more info on the specific version of ESXi you upgrade from/to and the configs you used to initialize vmxnet3 pmd?
If this is 5.5U3, by any chance you are using a rx ring size that’s larger than 2048?
>
>VMXNET3_WRITE_BAR1_REG(hw, VMXNET3_REG_CMD, VMXNET3_CMD_ACTIVATE_DEV)
>status = VMXNET3_READ_BAR1_REG(hw, VMXNET3_REG_CMD);
>
>status is not 0, so device can not be activated.
>
>Has anybody got same problem?
>
>Thanks,
>Bin
>
>--
>This message is for the designated and authorized recipient only and may
>contain privileged, proprietary, confidential or otherwise private
>information relating to vArmour Networks, Inc. and is the sole property of
>vArmour Networks, Inc. Any views or opinions expressed are solely those of
>the author and do not necessarily represent those of vArmour Networks, Inc.
>If you have received this message in error, or if you are not authorized to
>receive it, please notify the sender immediately and delete the original
>message and any attachments from your system immediately. If you are not a
>designated or authorized recipient, any other use or retention of this
>message or its contents is prohibited.
prev parent reply other threads:[~2015-10-31 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 3:54 Bin Zhang
2015-10-31 9:11 ` Yong Wang [this message]
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=D1BB1E46-96E0-43C6-9D54-476016B79ED7@vmware.com \
--to=yongwang@vmware.com \
--cc=bzhang@varmour.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).