[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210506172021.7327-1-yannick.vignon@oss.nxp.com>
Date: Thu, 6 May 2021 19:20:19 +0200
From: Yannick Vignon <yannick.vignon@....nxp.com>
To: "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Eric Dumazet <edumazet@...gle.com>,
Antoine Tenart <atenart@...nel.org>,
Wei Wang <weiwan@...gle.com>, Taehee Yoo <ap420073@...il.com>,
Alexander Lobakin <alobakin@...me>, netdev@...r.kernel.org,
Giuseppe Cavallaro <peppe.cavallaro@...com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Jose Abreu <joabreu@...opsys.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Joakim Zhang <qiangqing.zhang@....com>,
sebastien.laveze@....nxp.com
Cc: Yannick Vignon <yannick.vignon@....com>
Subject: [RFC PATCH net-next v1 0/2] Threaded NAPI configurability
From: Yannick Vignon <yannick.vignon@....com>
The purpose of these 2 patches is to be able to configure the scheduling
properties (e.g. affinity, priority...) of the NAPI threads more easily
at run-time, based on the hardware queues each thread is handling.
The main goal is really to expose which thread does what, as the current
naming doesn't exactly make that clear.
Posting this as an RFC in case people have different opinions on how to
do that.
Yannick Vignon (2):
net: add name field to napi struct
net: stmmac: use specific name for each NAPI instance
.../net/ethernet/stmicro/stmmac/stmmac_main.c | 21 ++++++----
include/linux/netdevice.h | 42 ++++++++++++++++++-
net/core/dev.c | 20 +++++++--
3 files changed, 69 insertions(+), 14 deletions(-)
--
2.17.1
Powered by blists - more mailing lists