From: Balazs Nemeth <bnemeth@redhat.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Potential regression introduced by commit b10231aed1edb9
Date: Fri, 18 Dec 2020 14:34:35 +0100 [thread overview]
Message-ID: <cb50e03150ff086ac5aef9487d65f33d7cd13899.camel@redhat.com> (raw)
Hi,
Commit b10231aed1edb9 introduces a regression on my systems. I have a
"QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller" which
relies on the qede driver. Calling rte_eth_promiscuous_enable(portid)
followed by rte_eth_allmulticast_enable(port_id) causes no packets to
arrive from my generator. It's important to add that the generator
doesn't specifically target the mac of the port. I presume that
irrespective of dst mac, if a port is put into promiscuous mode, all
packets should arrive and rte_eth_allmulticast_enable should not cause
*less* packets to arrive. Am I missing something? It seems that
b10231aed1edb9 inadvertently introduced either a bug or a pretty
significant change in semantics (at least for qede)?
Regards,
Balazs
next reply other threads:[~2020-12-18 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 13:34 Balazs Nemeth [this message]
2020-12-29 13:29 ` Igor Russkikh
2020-12-30 12:51 ` Devendra Singh Rawat
2020-12-30 12:55 ` Balazs Nemeth
2021-01-04 12:03 ` Ferruh Yigit
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=cb50e03150ff086ac5aef9487d65f33d7cd13899.camel@redhat.com \
--to=bnemeth@redhat.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).