[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9bc9ff1c-13c5-f01c-ede2-b5cd21c09a38@gmail.com>
Date: Mon, 21 Dec 2020 14:33:16 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...il.com>,
"bcm-kernel-feedback-list@...adcom.com"
<bcm-kernel-feedback-list@...adcom.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [RFC PATCH net-next 3/4] net: systemport: use standard netdevice
notifier to detect DSA presence
On 12/20/2020 8:53 PM, Florian Fainelli wrote:
>
> The call to netif_set_real_num_tx_queues() succeeds and
> slave_dev->real_num_tx_queues is changed to 4 accordingly. The loop that
> assigns the internal queue mapping (priv->ring_map) is correctly limited
> to 4, however we get two calls per switch port instead of one. I did not
> have much time to debug why we get called twice but I will be looking
> into this tomorrow.
There was not any bug other than there are two instances of a SYSTEMPORT
device in my system and they both receive the same notification.
So we do need to qualify which of the notifier block matches the device
of interest, because if we do extract the private structure from the
device being notified, it is always going to match.
Incremental fixup here:
https://github.com/ffainelli/linux/commit/0eea16e706a73c56a36d701df483ff73211aae7f
and you can add Tested-by: Florian Fainelli <f.fainelli@...il.com> when
you resubmit.
Thanks, this is a really nice cleanup.
--
Florian
Powered by blists - more mailing lists