DPDK patches and discussions
 help / color / mirror / Atom feed
From: Igor Russkikh <irusskikh@marvell.com>
To: Balazs Nemeth <bnemeth@redhat.com>, <dev@dpdk.org>,
	Devendra Singh Rawat <dsinghrawat@marvell.com>,
	Rasesh Mody <rmody@marvell.com>
Subject: Re: [dpdk-dev] Potential regression introduced by commit b10231aed1edb9
Date: Tue, 29 Dec 2020 14:29:37 +0100
Message-ID: <8a90fc3e-31dd-2792-0dee-7c86523f2245@marvell.com> (raw)
In-Reply-To: <cb50e03150ff086ac5aef9487d65f33d7cd13899.camel@redhat.com>

Hi Balazs,

This could be a regression for your specific usecase.

The commit itself tried to fix promisc as is.

Adding more people to comment/investigate here.

Devendra, could it be that we don't consider subsequent calls of
promisc_enabled + allmulti_enable ?

On 18/12/2020 2:34 pm, Balazs Nemeth wrote:
> 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
> 

  reply	other threads:[~2020-12-29 13:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18 13:34 Balazs Nemeth
2020-12-29 13:29 ` Igor Russkikh [this message]
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=8a90fc3e-31dd-2792-0dee-7c86523f2245@marvell.com \
    --to=irusskikh@marvell.com \
    --cc=bnemeth@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dsinghrawat@marvell.com \
    --cc=rmody@marvell.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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git