From: Amiya Mohakud <amohakud@paloaltonetworks.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Jochen Behrens <jbehrens@vmware.com>, dev@dpdk.org, pagupta@vmware.com
Subject: Re: [Bug 1209] vmxnet3 interface not receiving any packets with dpdk-22.11.1
Date: Mon, 3 Apr 2023 14:53:11 +0530 [thread overview]
Message-ID: <CAC6kMfMQEFB7oQ98X=Ycu6RRjqU1cQoLfVe+skQ9No5p=PZKUQ@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8ywtvZ88TxCp1MaLPFwh9b7VFqYtYvfLh9BCCO+_sF3UA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4009 bytes --]
Hi Jochen,
Could you please help here?
Regards
Amiya
On Fri, Mar 31, 2023 at 1:10 PM David Marchand <david.marchand@redhat.com>
wrote:
> Hello Jochen,
>
> On Fri, Mar 31, 2023 at 9:07 AM <bugzilla@dpdk.org> wrote:
> >
> > Bug ID 1209
> > Summary vmxnet3 interface not receiving any packets with dpdk-22.11.1
> > Product DPDK
> > Version 22.11
> > Hardware x86
> > OS All
> > Status UNCONFIRMED
> > Severity critical
> > Priority Normal
> > Component ethdev
> > Assignee dev@dpdk.org
> > Reporter amohakud@paloaltonetworks.com
> > Target Milestone ---
> >
> > Hi,
> > I recently upgraded our DPDK to 22.11.1 and observed that the guest
> vmxnet3
> > interface is not receiving any unicast packets. It's able to receive the
> > broadcast packets though. We enable promiscuous and all-multicast on the
> port.
> >
> > rte_eth_promiscuous_enable(port);
> > rte_eth_allmulticast_enable(port);
> >
> > This happens when the vswitch has only 2 ports attached.
> >
> > On further triaging,
> > - I could find out that on the same setup, dpdk-20.11 works fine.
> > - Upon comparing the working scenario and non-working scenario on esx
> host, I
> > could notice that there is some difference in port configuration of
> vswitch.
> >
> > Below is the snapshot of working case, where the ethFRP:frame routing {
> > requested:filter flags is 0x1d.
> >
> > port {
> > port index:365
> > vnic index:0x00000003
> > portCfg:build_1_15_2_vm-v3--p1e3-u2e3
> > dvPortId:
> > clientName:sjc-cms-esx15-csm02-pan1
> > clientType: 5 -> VMM Virtual NIC
> > clientSubType: 9 -> Vmxnet3 Client
> > world leader:2120158
> > flags: 0x40013 -> IN_USE ENABLED WORLD_ASSOC CONNECTED
> > Impl customized blocked flags:0x00000000
> > Passthru status: 0x8 -> DISABLED_BY_HOST
> > fixed Hw Id:00:50:56:b8:20:aa:
> > ethFRP:frame routing {
> > requested:filter {
> > flags:0x0000001d
> > unicastAddr:00:50:56:b8:20:aa:
> > numMulticastAddresses:0
> > multicastAddresses:
> > LADRF:[0]: 0x0
> > [1]: 0x0
> > }
> > accepted:filter {
> > flags:0x0000001d
> > unicastAddr:00:50:56:b8:20:aa:
> > numMulticastAddresses:0
> > multicastAddresses:
> > LADRF:[0]: 0x0
> > [1]: 0x0
> > }
> > }
> >
> >
> > For the non-working case the flag is set to 0x09.
> >
> > port {
> > port index:365
> > vnic index:0x00000003
> > portCfg:build_1_15_2_vm-v3--p1e3-u2e3
> > dvPortId:
> > clientName:sjc-cms-esx15-csm02-pan1
> > clientType: 5 -> VMM Virtual NIC
> > clientSubType: 9 -> Vmxnet3 Client
> > world leader:2120158
> > flags: 0x40013 -> IN_USE ENABLED WORLD_ASSOC CONNECTED
> > Impl customized blocked flags:0x00000000
> > Passthru status: 0x8 -> DISABLED_BY_HOST
> > fixed Hw Id:00:50:56:b8:20:aa:
> > ethFRP:frame routing {
> > requested:filter {
> > flags:0x00000009
> > unicastAddr:00:50:56:b8:20:aa:
> > numMulticastAddresses:0
> > multicastAddresses:
> > LADRF:[0]: 0x0
> > [1]: 0x0
> > }
> > accepted:filter {
> > flags:0x00000009
> > unicastAddr:00:50:56:b8:20:aa:
> > numMulticastAddresses:0
> > multicastAddresses:
> > LADRF:[0]: 0x0
> > [1]: 0x0
> > }
> > }
> > filter supported features: 0 -> NONE
> > filter properties: 0 -> NONE
> > rx mode: 0 -> INLINE
> > tune mode: 0 -> default
> > fastpath switch ID:0xffffffff
> > fastpath port ID:0xffffffff
> > }
> >
> > I think these are some of the flags set by vmxnet3 device and in
> dpdk-22.11,
> > its not updating the flags.
>
> As a maintainer of the net/vmxnet3 driver, could you please register
> to bugzilla?
> And please have a look.
>
>
> Thanks!
>
> --
> David marchand
>
>
[-- Attachment #2: Type: text/html, Size: 5724 bytes --]
prev parent reply other threads:[~2023-04-12 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 7:06 bugzilla
2023-03-31 7:40 ` David Marchand
2023-04-03 9:23 ` Amiya Mohakud [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='CAC6kMfMQEFB7oQ98X=Ycu6RRjqU1cQoLfVe+skQ9No5p=PZKUQ@mail.gmail.com' \
--to=amohakud@paloaltonetworks.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jbehrens@vmware.com \
--cc=pagupta@vmware.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).