From: patchwork-bot+netdevbpf@kernel.org
To: Hariprasad Kelam <hkelam@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
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, pabeni@redhat.com, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, maxtram95@gmail.com,
corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [net-next PatchV4 0/4] octeontx2-pf: support Round Robin scheduling
Date: Fri, 21 Jul 2023 09:00:23 +0000 [thread overview]
Message-ID: <168993002358.14749.10687127850006488208.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230719110443.15310-1-hkelam@marvell.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 19 Jul 2023 16:34:39 +0530 you wrote:
> octeontx2 and CN10K silicons support Round Robin scheduling. When multiple
> traffic flows reach transmit level with the same priority, with Round Robin
> scheduling traffic flow with the highest quantum value is picked. With this
> support, the user can add multiple classes with the same priority and
> different quantum in htb offload.
>
> This series of patches adds support for the same.
>
> [...]
Here is the summary with links:
- [net-next,PatchV4,1/4] octeontx2-pf: implement transmit schedular allocation algorithm
https://git.kernel.org/netdev/net-next/c/f78dca691287
- [net-next,PatchV4,2/4] sch_htb: Allow HTB quantum parameter in offload mode
https://git.kernel.org/netdev/net-next/c/9fe63d5f1da9
- [net-next,PatchV4,3/4] octeontx2-pf: htb offload support for Round Robin scheduling
https://git.kernel.org/netdev/net-next/c/47a9656f168a
- [net-next,PatchV4,4/4] docs: octeontx2: extend documentation for Round Robin scheduling
https://git.kernel.org/netdev/net-next/c/6f71051ffbdb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-07-21 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 11:04 [net-next PatchV4 0/4] octeontx2-pf: support Round Robin scheduling Hariprasad Kelam
2023-07-19 11:04 ` [net-next PatchV4 1/4] octeontx2-pf: implement transmit schedular allocation algorithm Hariprasad Kelam
2023-07-19 11:04 ` [net-next PatchV4 2/4] sch_htb: Allow HTB quantum parameter in offload mode Hariprasad Kelam
2023-07-19 11:04 ` [net-next PatchV4 3/4] octeontx2-pf: htb offload support for Round Robin scheduling Hariprasad Kelam
2023-07-19 11:04 ` [net-next PatchV4 4/4] docs: octeontx2: extend documentation " Hariprasad Kelam
2023-07-21 9:00 ` patchwork-bot+netdevbpf [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=168993002358.14749.10687127850006488208.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxtram95@gmail.com \
--cc=naveenm@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 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.