Hi,
When configuring the vmxnet3 based ethernet device, the RX VLAN Strip offload
does not work as it usually does with other real NICs which support this
function.
When configuring with rxmode.hw_vlan_strip = 1, the ipackets statistic does not
increase when a VLAN ether type frame is received
When configuring the vmxnet3 based ethernet device, the VLAN Strip RX offload
does not work as it usually does with other real NICs.
When configuring with rxmode.hw_vlan_strip = 1, the ipackets statistic does not
increase when a VLAN ether type frame is received on the port and it is also
not r
+ Yong Wang - new maintainer for vmxnet3 pod
> On 06-Apr-2018, at 7:21 PM, Padam Jeet Singh wrote:
>
> Hi,
>
> When configuring the vmxnet3 based ethernet device, the RX VLAN Strip offload
> does not work as it usually does with other real NICs which support this
> function.
>
> When configu
Padam,
As far as I know, this feature works. What DPDK version did you use? Is there
any port reconfiguration (stop/start/mtu change, etc) that could lose your vlan
offload settings (a dump of the port config at runtime will be able to confirm
this)? Can you also post a snippet of packet cap
> On 06-Apr-2018, at 11:12 PM, Yong Wang wrote:
>
> Padam,
>
> As far as I know, this feature works. What DPDK version did you use?
DPDK Version 17.05
> Is there any port reconfiguration (stop/start/mtu change, etc) that could
> lose your vlan offload settings (a dump of the port config at
When using 4095, I assume you enabled trunk mode on ESX vswitch. What ESX
version did you use? Is the vswitch standard switch or DVS? We have tested over
ESX6.0 and onwards plus DPDK 17.05 and it should work.
On 4/8/18, 11:22 PM, "Padam Jeet Singh" wrote:
> On 06-Apr-2018, at 11:12
> On 10-Apr-2018, at 11:43 AM, Yong Wang wrote:
>
> When using 4095, I assume you enabled trunk mode on ESX vswitch. What ESX
> version did you use? Is the vswitch standard switch or DVS? We have tested
> over ESX6.0 and onwards plus DPDK 17.05 and it should work.
Yes, the 4095 enables trun
Hi,
Does anyone have a work-around for this? Should we debug the vmxnet3 driver
since for sure this issue is even coming in standard l2fwd example.
Thanks,
Padam
> On 12-Apr-2018, at 11:52 AM, Padam Jeet Singh
> wrote:
>
>
>
>> On 10-Apr-2018, at 11:43 AM, Yong Wang wrote:
>>
>> When usi
8 matches
Mail list logo
