[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CO6PR18MB3873B6957F4CD2430C288C4EB0AC9@CO6PR18MB3873.namprd18.prod.outlook.com>
Date: Sun, 10 Jan 2021 18:38:59 +0000
From: Stefan Chulski <stefanc@...vell.com>
To: Russell King - ARM Linux admin <linux@...linux.org.uk>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"thomas.petazzoni@...tlin.com" <thomas.petazzoni@...tlin.com>,
"davem@...emloft.net" <davem@...emloft.net>,
Nadav Haklai <nadavh@...vell.com>,
Yan Markman <ymarkman@...vell.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kuba@...nel.org" <kuba@...nel.org>,
"mw@...ihalf.com" <mw@...ihalf.com>,
"andrew@...n.ch" <andrew@...n.ch>,
"atenart@...nel.org" <atenart@...nel.org>
Subject: RE: [EXT] Re: [PATCH RFC net-next 11/19] net: mvpp2: add flow
control RXQ and BM pool config callbacks
> Sorry, but that is not really a decision the driver can make. It is part of a kernel
> that _does_ support CPU hotplug, and the online CPUs can be changed today.
>
> It is likely that every distro out there builds the kernel with CPU hotplug
> enabled.
>
> If changing the online CPUs causes the driver to misbehave, that is a(nother)
> bug with the driver.
This function doesn't really need to know num_active_cpus, only host ID used by
used by shared RX interrupt in single queue mode.
Host ID is just register address space used to access PPv2 register space.
So I can remove this use of num_active_cpus.
Stefan,
Regards.
Powered by blists - more mailing lists