| /linux/drivers/net/wireless/mediatek/mt76/mt7615/ |
| H A D | dma.c | aa40528a5bca990ef8f6a82eb26d23c81b4b3cff Sun Jul 26 11:09:51 UTC 2020 Felix Fietkau <nbd@nbd.name> mt76: use threaded NAPI
With threaded NAPI, the rx handler function is no longer bound to the CPU that
fired the interrupt, which significantly helps to spread the workload over
multiple CPUs, especially when multiple devices are using threaded NAPI at the
same time.
Exclude the tx handler from threaded NAPI by using a separate dummy netdev.
The work is small and short-lived enough that it makes more sense to run it in
softirq instead of creating a dedicated thread
Signed-off-by: Felix Fietkau <nbd@nbd.name>
aa40528a5bca990ef8f6a82eb26d23c81b4b3cff Sun Jul 26 11:09:51 UTC 2020 Felix Fietkau <nbd@nbd.name> mt76: use threaded NAPI
With threaded NAPI, the rx handler function is no longer bound to the CPU that
fired the interrupt, which significantly helps to spread the workload over
multiple CPUs, especially when multiple devices are using threaded NAPI at the
same time.
Exclude the tx handler from threaded NAPI by using a separate dummy netdev.
The work is small and short-lived enough that it makes more sense to run it in
softirq instead of creating a dedicated thread
Signed-off-by: Felix Fietkau <nbd@nbd.name>
|
| /linux/drivers/net/wireless/mediatek/mt76/mt7603/ |
| H A D | dma.c | aa40528a5bca990ef8f6a82eb26d23c81b4b3cff Sun Jul 26 11:09:51 UTC 2020 Felix Fietkau <nbd@nbd.name> mt76: use threaded NAPI
With threaded NAPI, the rx handler function is no longer bound to the CPU that
fired the interrupt, which significantly helps to spread the workload over
multiple CPUs, especially when multiple devices are using threaded NAPI at the
same time.
Exclude the tx handler from threaded NAPI by using a separate dummy netdev.
The work is small and short-lived enough that it makes more sense to run it in
softirq instead of creating a dedicated thread
Signed-off-by: Felix Fietkau <nbd@nbd.name>
aa40528a5bca990ef8f6a82eb26d23c81b4b3cff Sun Jul 26 11:09:51 UTC 2020 Felix Fietkau <nbd@nbd.name> mt76: use threaded NAPI
With threaded NAPI, the rx handler function is no longer bound to the CPU that
fired the interrupt, which significantly helps to spread the workload over
multiple CPUs, especially when multiple devices are using threaded NAPI at the
same time.
Exclude the tx handler from threaded NAPI by using a separate dummy netdev.
The work is small and short-lived enough that it makes more sense to run it in
softirq instead of creating a dedicated thread
Signed-off-by: Felix Fietkau <nbd@nbd.name>
|
| /linux/drivers/net/wireless/mediatek/mt76/mt7915/ |
| H A D | dma.c | aa40528a5bca990ef8f6a82eb26d23c81b4b3cff Sun Jul 26 11:09:51 UTC 2020 Felix Fietkau <nbd@nbd.name> mt76: use threaded NAPI
With threaded NAPI, the rx handler function is no longer bound to the CPU that
fired the interrupt, which significantly helps to spread the workload over
multiple CPUs, especially when multiple devices are using threaded NAPI at the
same time.
Exclude the tx handler from threaded NAPI by using a separate dummy netdev.
The work is small and short-lived enough that it makes more sense to run it in
softirq instead of creating a dedicated thread
Signed-off-by: Felix Fietkau <nbd@nbd.name>
aa40528a5bca990ef8f6a82eb26d23c81b4b3cff Sun Jul 26 11:09:51 UTC 2020 Felix Fietkau <nbd@nbd.name> mt76: use threaded NAPI
With threaded NAPI, the rx handler function is no longer bound to the CPU that
fired the interrupt, which significantly helps to spread the workload over
multiple CPUs, especially when multiple devices are using threaded NAPI at the
same time.
Exclude the tx handler from threaded NAPI by using a separate dummy netdev.
The work is small and short-lived enough that it makes more sense to run it in
softirq instead of creating a dedicated thread
Signed-off-by: Felix Fietkau <nbd@nbd.name>
|
| /linux/drivers/net/wireless/mediatek/mt76/ |
| H A D | mt76x02_mmio.c | aa40528a5bca990ef8f6a82eb26d23c81b4b3cff Sun Jul 26 11:09:51 UTC 2020 Felix Fietkau <nbd@nbd.name> mt76: use threaded NAPI
With threaded NAPI, the rx handler function is no longer bound to the CPU that
fired the interrupt, which significantly helps to spread the workload over
multiple CPUs, especially when multiple devices are using threaded NAPI at the
same time.
Exclude the tx handler from threaded NAPI by using a separate dummy netdev.
The work is small and short-lived enough that it makes more sense to run it in
softirq instead of creating a dedicated thread
Signed-off-by: Felix Fietkau <nbd@nbd.name>
aa40528a5bca990ef8f6a82eb26d23c81b4b3cff Sun Jul 26 11:09:51 UTC 2020 Felix Fietkau <nbd@nbd.name> mt76: use threaded NAPI
With threaded NAPI, the rx handler function is no longer bound to the CPU that
fired the interrupt, which significantly helps to spread the workload over
multiple CPUs, especially when multiple devices are using threaded NAPI at the
same time.
Exclude the tx handler from threaded NAPI by using a separate dummy netdev.
The work is small and short-lived enough that it makes more sense to run it in
softirq instead of creating a dedicated thread
Signed-off-by: Felix Fietkau <nbd@nbd.name>
|
| H A D | dma.c | aa40528a5bca990ef8f6a82eb26d23c81b4b3cff Sun Jul 26 11:09:51 UTC 2020 Felix Fietkau <nbd@nbd.name> mt76: use threaded NAPI
With threaded NAPI, the rx handler function is no longer bound to the CPU that
fired the interrupt, which significantly helps to spread the workload over
multiple CPUs, especially when multiple devices are using threaded NAPI at the
same time.
Exclude the tx handler from threaded NAPI by using a separate dummy netdev.
The work is small and short-lived enough that it makes more sense to run it in
softirq instead of creating a dedicated thread
Signed-off-by: Felix Fietkau <nbd@nbd.name>
aa40528a5bca990ef8f6a82eb26d23c81b4b3cff Sun Jul 26 11:09:51 UTC 2020 Felix Fietkau <nbd@nbd.name> mt76: use threaded NAPI
With threaded NAPI, the rx handler function is no longer bound to the CPU that
fired the interrupt, which significantly helps to spread the workload over
multiple CPUs, especially when multiple devices are using threaded NAPI at the
same time.
Exclude the tx handler from threaded NAPI by using a separate dummy netdev.
The work is small and short-lived enough that it makes more sense to run it in
softirq instead of creating a dedicated thread
Signed-off-by: Felix Fietkau <nbd@nbd.name>
|
| H A D | mt76.h | aa40528a5bca990ef8f6a82eb26d23c81b4b3cff Sun Jul 26 11:09:51 UTC 2020 Felix Fietkau <nbd@nbd.name> mt76: use threaded NAPI
With threaded NAPI, the rx handler function is no longer bound to the CPU that
fired the interrupt, which significantly helps to spread the workload over
multiple CPUs, especially when multiple devices are using threaded NAPI at the
same time.
Exclude the tx handler from threaded NAPI by using a separate dummy netdev.
The work is small and short-lived enough that it makes more sense to run it in
softirq instead of creating a dedicated thread
Signed-off-by: Felix Fietkau <nbd@nbd.name>
aa40528a5bca990ef8f6a82eb26d23c81b4b3cff Sun Jul 26 11:09:51 UTC 2020 Felix Fietkau <nbd@nbd.name> mt76: use threaded NAPI
With threaded NAPI, the rx handler function is no longer bound to the CPU that
fired the interrupt, which significantly helps to spread the workload over
multiple CPUs, especially when multiple devices are using threaded NAPI at the
same time.
Exclude the tx handler from threaded NAPI by using a separate dummy netdev.
The work is small and short-lived enough that it makes more sense to run it in
softirq instead of creating a dedicated thread
Signed-off-by: Felix Fietkau <nbd@nbd.name>
|