Netdev List
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Ratheesh Kannoth <rkannoth@marvell.com>
Cc: <bpf@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<netdev@vger.kernel.org>, <andrew+netdev@lunn.ch>,
	<ast@kernel.org>, <daniel@iogearbox.net>, <davem@davemloft.net>,
	<edumazet@google.com>, <hawk@kernel.org>,
	<john.fastabend@gmail.com>, <pabeni@redhat.com>,
	<sdf@fomichev.me>, <sgoutham@marvell.com>
Subject: Re: [PATCH v12 net-next] octeontx2-pf: add mqprio bandwidth offload for NIX TX schedulers
Date: Fri, 4 Sep 2026 14:21:08 -0700	[thread overview]
Message-ID: <20260904142108.72652338@kernel.org> (raw)
In-Reply-To: <apo3CVfUw2-aXF8F@rkannoth-OptiPlex-7090>

On Fri, 4 Sep 2026 08:42:09 +0530 Ratheesh Kannoth wrote:
> On 2026-09-03 at 08:03:24, Ratheesh Kannoth (rkannoth@marvell.com) wrote:
> > Add TC_SETUP_QDISC_MQPRIO offload for channel-mode mqprio with
> > TC_MQPRIO_SHAPER_BW_RATE. Program per-queue MDQ CIR/PIR through the
> > NIX TX scheduler mailbox for each non-QoS transmit queue. When offload
> > is active, allocate one SMQ per such queue, parent every MDQ under
> > TL4[0], and map each traffic class min/max rate to the queue(s) in that
> > class.  
> 
> will address sashiko comments in v13

Please wait for netdev-ai report before you respin
https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260903023324.3078284-1-rkannoth@marvell.com
It seems to have found 5 more issues 

Yes the embargo is really long for you, because it takes you 10+
revisions to get anything merged.

      reply	other threads:[~2026-09-04 21:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  2:33 [PATCH v12 net-next] octeontx2-pf: add mqprio bandwidth offload for NIX TX schedulers Ratheesh Kannoth
2026-09-04  3:12 ` Ratheesh Kannoth
2026-09-04 21:21   ` Jakub Kicinski [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=20260904142108.72652338@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rkannoth@marvell.com \
    --cc=sdf@fomichev.me \
    --cc=sgoutham@marvell.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