From: Yannick Vignon <yannick.vignon@oss.nxp.com>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Antoine Tenart <atenart@kernel.org>, Wei Wang <weiwan@google.com>,
Taehee Yoo <ap420073@gmail.com>,
Alexander Lobakin <alobakin@pm.me>,
netdev@vger.kernel.org,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Joakim Zhang <qiangqing.zhang@nxp.com>,
sebastien.laveze@oss.nxp.com
Cc: Yannick Vignon <yannick.vignon@nxp.com>
Subject: [RFC PATCH net-next v1 0/2] Threaded NAPI configurability
Date: Thu, 6 May 2021 19:20:19 +0200 [thread overview]
Message-ID: <20210506172021.7327-1-yannick.vignon@oss.nxp.com> (raw)
From: Yannick Vignon <yannick.vignon@nxp.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
next reply other threads:[~2021-05-06 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 17:20 Yannick Vignon [this message]
2021-05-06 17:20 ` [RFC PATCH net-next v1 1/2] net: add name field to napi struct Yannick Vignon
2021-05-06 17:35 ` Eric Dumazet
2021-05-11 16:44 ` Yannick Vignon
2021-05-06 17:20 ` [RFC PATCH net-next v1 2/2] net: stmmac: use specific name for each NAPI instance Yannick Vignon
2021-05-06 22:18 ` [RFC PATCH net-next v1 0/2] Threaded NAPI configurability Jakub Kicinski
2021-05-11 16:46 ` Yannick Vignon
2021-05-12 1:07 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210506172021.7327-1-yannick.vignon@oss.nxp.com \
--to=yannick.vignon@oss.nxp.com \
--cc=alexandre.torgue@foss.st.com \
--cc=alobakin@pm.me \
--cc=ap420073@gmail.com \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=qiangqing.zhang@nxp.com \
--cc=sebastien.laveze@oss.nxp.com \
--cc=weiwan@google.com \
--cc=yannick.vignon@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.