From: Paolo Abeni <pabeni@redhat.com>
To: Hariprasad Kelam <hkelam@marvell.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kuba@kernel.org, davem@davemloft.net,
willemdebruijn.kernel@gmail.com, andrew@lunn.ch,
sgoutham@marvell.com, lcherian@marvell.com, gakula@marvell.com,
jerinj@marvell.com, sbhatta@marvell.com, naveenm@marvell.com,
edumazet@google.com, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
jiri@resnulli.us, maxtram95@gmail.com, corbet@lwn.net
Subject: Re: [net-next Patch v10 0/8] octeontx2-pf: HTB offload support
Date: Thu, 27 Apr 2023 08:18:44 +0200 [thread overview]
Message-ID: <69928a2f43bea996380fa311a38ab0d1e4cdcf08.camel@redhat.com> (raw)
In-Reply-To: <20230426054731.5720-1-hkelam@marvell.com>
On Wed, 2023-04-26 at 11:17 +0530, Hariprasad Kelam wrote:
> octeontx2 silicon and CN10K transmit interface consists of five
> transmit levels starting from MDQ, TL4 to TL1. Once packets are
> submitted to MDQ, hardware picks all active MDQs using strict
> priority, and MDQs having the same priority level are chosen using
> round robin. Each packet will traverse MDQ, TL4 to TL1 levels.
> Each level contains an array of queues to support scheduling and
> shaping.
>
> As HTB supports classful queuing mechanism by supporting rate and
> ceil and allow the user to control the absolute bandwidth to
> particular classes of traffic the same can be achieved by
> configuring shapers and schedulers on different transmit levels.
## Form letter - net-next-closed
The merge window for v6.3 has begun and therefore net-next is closed
for new drivers, features, code refactoring and optimizations.
We are currently accepting bug fixes only.
Please repost when net-next reopens after May 8th.
RFC patches sent for review only are obviously welcome at any time.
--
pw-bot: defer
next prev parent reply other threads:[~2023-04-27 6:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 5:47 Hariprasad Kelam
2023-04-26 5:47 ` [net-next Patch v10 1/8] sch_htb: Allow HTB priority parameter in offload mode Hariprasad Kelam
2023-04-26 5:47 ` [net-next Patch v10 2/8] octeontx2-pf: Rename tot_tx_queues to non_qos_queues Hariprasad Kelam
2023-04-26 5:47 ` [net-next Patch v10 3/8] octeontx2-pf: qos send queues management Hariprasad Kelam
2023-04-26 5:47 ` [net-next Patch v10 4/8] octeontx2-pf: Refactor schedular queue alloc/free calls Hariprasad Kelam
2023-04-26 5:47 ` [net-next Patch v10 5/8] octeontx2-pf: Prepare for QOS offload Hariprasad Kelam
2023-04-26 5:47 ` [net-next Patch v10 6/8] octeontx2-pf: Add support for HTB offload Hariprasad Kelam
2023-04-26 5:47 ` [net-next Patch v10 7/8] octeontx2-pf: ethtool expose qos stats Hariprasad Kelam
2023-04-26 5:47 ` [net-next Patch v10 8/8] docs: octeontx2: Add Documentation for QOS Hariprasad Kelam
2023-04-27 6:18 ` Paolo Abeni [this message]
2023-05-13 8:51 [net-next Patch v10 0/8] octeontx2-pf: HTB offload support Hariprasad Kelam
2023-05-15 8:40 ` patchwork-bot+netdevbpf
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=69928a2f43bea996380fa311a38ab0d1e4cdcf08.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxtram95@gmail.com \
--cc=naveenm@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xiyou.wangcong@gmail.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
all inboxes | Powered by JetHome®