From: Furong Xu <0x1207@gmail.com>
To: Serge Semin <fancer.lancer@gmail.com>,
Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Joao Pinto <jpinto@synopsys.com>
Cc: netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, xfr@outlook.com, rock.xu@nio.com,
Furong Xu <0x1207@gmail.com>
Subject: [PATCH net-next v2 0/7] net: stmmac: FPE via ethtool + tc
Date: Tue, 13 Aug 2024 19:47:26 +0800 [thread overview]
Message-ID: <cover.1723548320.git.0x1207@gmail.com> (raw)
Move the Frame Preemption(FPE) over to the new standard API which uses
ethtool-mm/tc-mqprio/tc-taprio.
Changes in v2:
1. refactor FPE verification processe
2. suspend/resume and kselftest-ethtool_mm, all test cases passed
3. handle TC:TXQ remapping for DWMAC CORE4+
Furong Xu (7):
net: stmmac: move stmmac_fpe_cfg to stmmac_priv data
net: stmmac: drop stmmac_fpe_handshake
net: stmmac: refactor FPE verification processe
net: stmmac: configure FPE via ethtool-mm
net: stmmac: support fp parameter of tc-mqprio
net: stmmac: support fp parameter of tc-taprio
net: stmmac: silence FPE kernel logs
.../net/ethernet/stmicro/stmmac/dwmac4_core.c | 10 +-
drivers/net/ethernet/stmicro/stmmac/dwmac5.c | 96 +++++++++-
drivers/net/ethernet/stmicro/stmmac/dwmac5.h | 11 +-
.../ethernet/stmicro/stmmac/dwxgmac2_core.c | 4 +-
drivers/net/ethernet/stmicro/stmmac/hwif.h | 20 +-
drivers/net/ethernet/stmicro/stmmac/stmmac.h | 22 +++
.../ethernet/stmicro/stmmac/stmmac_ethtool.c | 103 +++++++++++
.../net/ethernet/stmicro/stmmac/stmmac_main.c | 173 +++++++++---------
.../net/ethernet/stmicro/stmmac/stmmac_tc.c | 115 ++++++++----
include/linux/stmmac.h | 28 ---
10 files changed, 416 insertions(+), 166 deletions(-)
--
2.34.1
next reply other threads:[~2024-08-13 11:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 11:47 Furong Xu [this message]
2024-08-13 11:47 ` [PATCH net-next v2 1/7] net: stmmac: move stmmac_fpe_cfg to stmmac_priv data Furong Xu
2024-08-13 11:47 ` [PATCH net-next v2 2/7] net: stmmac: drop stmmac_fpe_handshake Furong Xu
2024-08-13 11:47 ` [PATCH net-next v2 3/7] net: stmmac: refactor FPE verification processe Furong Xu
2024-08-13 11:47 ` [PATCH net-next v2 4/7] net: stmmac: configure FPE via ethtool-mm Furong Xu
2024-08-13 11:47 ` [PATCH net-next v2 5/7] net: stmmac: support fp parameter of tc-mqprio Furong Xu
2024-08-13 11:47 ` [PATCH net-next v2 6/7] net: stmmac: support fp parameter of tc-taprio Furong Xu
2024-08-13 11:47 ` [PATCH net-next v2 7/7] net: stmmac: silence FPE kernel logs Furong Xu
2024-08-16 11:48 ` [PATCH net-next v2 0/7] net: stmmac: FPE via ethtool + tc Vladimir Oltean
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=cover.1723548320.git.0x1207@gmail.com \
--to=0x1207@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fancer.lancer@gmail.com \
--cc=joabreu@synopsys.com \
--cc=jpinto@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=rock.xu@nio.com \
--cc=xfr@outlook.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.