From: Vladimir Oltean <olteanv@gmail.com>
To: Furong Xu <0x1207@gmail.com>
Cc: Alexander Lobakin <aleksander.lobakin@intel.com>,
Serge Semin <fancer.lancer@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>,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, rmk+kernel@armlinux.org.uk,
linux@armlinux.org.uk, xfr@outlook.com
Subject: Re: [PATCH net-next v8 6/7] net: stmmac: support fp parameter of tc-taprio
Date: Thu, 5 Sep 2024 17:52:28 +0300 [thread overview]
Message-ID: <20240905145228.raglhbpikfxolgrw@skbuf> (raw)
In-Reply-To: <55067bfa505933731cbd018d19213b89126321e3.1725518136.git.0x1207@gmail.com> <55067bfa505933731cbd018d19213b89126321e3.1725518136.git.0x1207@gmail.com>
On Thu, Sep 05, 2024 at 03:02:27PM +0800, Furong Xu wrote:
> tc-taprio can select whether traffic classes are express or preemptible.
>
> 0) tc qdisc add dev eth1 parent root handle 100 taprio \
> num_tc 4 \
> map 0 1 2 3 2 2 2 2 2 2 2 2 2 2 2 3 \
> queues 1@0 1@1 1@2 1@3 \
> base-time 1000000000 \
> sched-entry S 03 10000000 \
> sched-entry S 0e 10000000 \
> flags 0x2 fp P E E E
>
> 1) After some traffic tests, MAC merge layer statistics are all good.
>
> Local device:
> [ {
> "ifname": "eth1",
> "pmac-enabled": true,
> "tx-enabled": true,
> "tx-active": true,
> "tx-min-frag-size": 60,
> "rx-min-frag-size": 60,
> "verify-enabled": true,
> "verify-time": 100,
> "max-verify-time": 128,
> "verify-status": "SUCCEEDED",
> "statistics": {
> "MACMergeFrameAssErrorCount": 0,
> "MACMergeFrameSmdErrorCount": 0,
> "MACMergeFrameAssOkCount": 0,
> "MACMergeFragCountRx": 0,
> "MACMergeFragCountTx": 17837,
> "MACMergeHoldCount": 18639
> }
> } ]
>
> Remote device:
> [ {
> "ifname": "end1",
> "pmac-enabled": true,
> "tx-enabled": true,
> "tx-active": true,
> "tx-min-frag-size": 60,
> "rx-min-frag-size": 60,
> "verify-enabled": true,
> "verify-time": 100,
> "max-verify-time": 128,
> "verify-status": "SUCCEEDED",
> "statistics": {
> "MACMergeFrameAssErrorCount": 0,
> "MACMergeFrameSmdErrorCount": 0,
> "MACMergeFrameAssOkCount": 17189,
> "MACMergeFragCountRx": 17837,
> "MACMergeFragCountTx": 0,
> "MACMergeHoldCount": 0
> }
> } ]
>
> Tested on DWMAC CORE 5.10a
>
> Signed-off-by: Furong Xu <0x1207@gmail.com>
> ---
Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
next prev parent reply other threads:[~2024-09-05 14:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 7:02 [PATCH net-next v8 0/7] net: stmmac: FPE via ethtool + tc Furong Xu
2024-09-05 7:02 ` [PATCH net-next v8 1/7] net: stmmac: move stmmac_fpe_cfg to stmmac_priv data Furong Xu
2024-09-05 7:02 ` [PATCH net-next v8 2/7] net: stmmac: drop stmmac_fpe_handshake Furong Xu
2024-09-05 7:02 ` [PATCH net-next v8 3/7] net: stmmac: refactor FPE verification process Furong Xu
2024-09-05 13:54 ` Vladimir Oltean
2024-09-05 14:58 ` Vladimir Oltean
2024-09-05 7:02 ` [PATCH net-next v8 4/7] net: stmmac: configure FPE via ethtool-mm Furong Xu
2024-09-05 7:02 ` [PATCH net-next v8 5/7] net: stmmac: support fp parameter of tc-mqprio Furong Xu
2024-09-05 14:02 ` Vladimir Oltean
2024-09-05 7:02 ` [PATCH net-next v8 6/7] net: stmmac: support fp parameter of tc-taprio Furong Xu
2024-09-05 14:52 ` Vladimir Oltean [this message]
2024-09-05 7:02 ` [PATCH net-next v8 7/7] net: stmmac: silence FPE kernel logs Furong Xu
2024-09-05 14:53 ` 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=20240905145228.raglhbpikfxolgrw@skbuf \
--to=olteanv@gmail.com \
--cc=0x1207@gmail.com \
--cc=aleksander.lobakin@intel.com \
--cc=alexandre.torgue@foss.st.com \
--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=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).