Re: [PATCH net-next] enetc: Use generic rule to map Tx rings to interrupt vectors

On Fri, 9 Apr 2021 13:19:52 +0300 Vladimir Oltean wrote:

On Fri, Apr 09, 2021 at 10:16:13AM +0300, Claudiu Manoil wrote:

quoted

Even if the current mapping is correct for the 1 CPU and 2 CPU cases
(currently enetc is included in SoCs with up to 2 CPUs only), better
use a generic rule for the mapping to cover all possible cases.
The number of CPUs is the same as the number of interrupt vectors:

Per device Tx rings -
device_tx_ring[idx], where idx = 0..n_rings_total-1

Per interrupt vector Tx rings -
int_vector[i].ring[j], where i = 0..n_int_vects-1
			     j = 0..n_rings_per_v-1

Mapping rule -
n_rings_per_v = n_rings_total / n_int_vects
for i = 0..n_int_vects - 1:
	for j = 0..n_rings_per_v - 1:
		idx = n_int_vects * j + i
		int_vector[i].ring[j] <- device_tx_ring[idx]

Signed-off-by: Claudiu Manoil <claudiu.manoil@nxp.com>

Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com>

Applied, thanks!