From: patchwork-bot+netdevbpf@kernel.org
To: Sunil Goutham <sgoutham@marvell.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org
Subject: Re: [net-next PATCH 0/2] cn10k: DWRR MTU and weights configuration
Date: Mon, 02 Aug 2021 14:10:06 +0000 [thread overview]
Message-ID: <162791340648.12354.1207492713207355529.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1627645754-18131-1-git-send-email-sgoutham@marvell.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 30 Jul 2021 17:19:12 +0530 you wrote:
> On OcteonTx2 DWRR quantum is directly configured into each of
> the transmit scheduler queues. And PF/VF drivers were free to
> config any value upto 2^24.
>
> On CN10K, HW is modified, the quantum configuration at scheduler
> queues is in terms of weight. And SW needs to setup a base DWRR MTU
> at NIX_AF_DWRR_RPM_MTU / NIX_AF_DWRR_SDP_MTU. HW will do
> 'DWRR MTU * weight' to get the quantum.
>
> [...]
Here is the summary with links:
- [net-next,1/2] octeontx2-af: cn10k: DWRR MTU configuration
https://git.kernel.org/netdev/net-next/c/76660df2b4a2
- [net-next,2/2] octeontx2-pf: cn10k: Config DWRR weight based on MTU
https://git.kernel.org/netdev/net-next/c/c39830a4ce4d
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:[~2021-08-02 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 11:49 [net-next PATCH 0/2] cn10k: DWRR MTU and weights configuration Sunil Goutham
2021-07-30 11:49 ` [net-next PATCH 1/2] octeontx2-af: cn10k: DWRR MTU configuration Sunil Goutham
2021-07-30 11:49 ` [net-next PATCH 2/2] octeontx2-pf: cn10k: Config DWRR weight based on MTU Sunil Goutham
2021-08-02 14:10 ` 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=162791340648.12354.1207492713207355529.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).