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

2021-04-09 Thread Jakub Kicinski
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: > > 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

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

2021-04-09 Thread Vladimir Oltean
On Fri, Apr 09, 2021 at 10:16:13AM +0300, Claudiu Manoil wrote: > 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

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

2021-04-09 Thread Claudiu Manoil
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_