From: Davide Caratti <dcaratti@redhat.com>
To: Lorenzo Bianconi <lorenzo.bianconi@oss.qualcomm.com>
Cc: Maxime Chevallier <maxime.chevallier@bootlin.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Daniel Thompson <daniel@riscstar.com>,
Alex Elder <elder@riscstar.com>,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net-next v2 0/2] Implement mqprio and ets qdisc offload in stmmac driver
Date: Fri, 7 Aug 2026 11:34:58 +0200 [thread overview]
Message-ID: <anWmwkIqEsOLFKXf@dcaratti.users.ipa.redhat.com> (raw)
In-Reply-To: <20260807-stmmac-ets-offload-v2-0-9ac67af92cb8@oss.qualcomm.com>
On Fri, Aug 07, 2026 at 10:41:38AM +0200, Lorenzo Bianconi wrote:
> ---
> Changes in v2:
> - Implement strict priority policy in mqprio qdisc offload
> - Restore to dt configured values destroying the qdisc
> - Do not ets offload if there are any queues in avb mode.
> - Re-apply ETS configuration closing/opening the net_device.
> - Link to v1: https://lore.kernel.org/r/20260804-stmmac-ets-offload-v1-1-f3a09169d22b@oss.qualcomm.com
Since SP and DWRR are mutually exclusive on this driver, here it makes
a lot more sense to fix semi-broken mq_prio offload on stmmac, and
let ETS offload DWRR-only setups. For the series:
Reviewed-by: Davide Caratti <dcaratti@redhat.com>
prev parent reply other threads:[~2026-08-07 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 8:41 [PATCH net-next v2 0/2] Implement mqprio and ets qdisc offload in stmmac driver Lorenzo Bianconi
2026-08-07 8:41 ` [PATCH net-next v2 1/2] net: stmmac: add tc-ets qdisc offload Lorenzo Bianconi
2026-08-07 8:41 ` [PATCH net-next v2 2/2] net: stmmac: add tc-mqprio " Lorenzo Bianconi
2026-08-07 9:34 ` Davide Caratti [this message]
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=anWmwkIqEsOLFKXf@dcaratti.users.ipa.redhat.com \
--to=dcaratti@redhat.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=daniel@riscstar.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elder@riscstar.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lorenzo.bianconi@oss.qualcomm.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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