From: Jakub Kicinski <kuba@kernel.org>
To: Hariprasad Kelam <hkelam@marvell.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.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 Patch v3 4/4] docs: octeontx2: extend documentation for Round Robin scheduling
Date: Tue, 18 Jul 2023 19:44:31 -0700 [thread overview]
Message-ID: <20230718194431.38c02846@kernel.org> (raw)
In-Reply-To: <20230717093319.26618-5-hkelam@marvell.com>
On Mon, 17 Jul 2023 15:03:19 +0530 Hariprasad Kelam wrote:
> +4. Create tc classes with same priorities and different quantum::
> +
> + # tc class add dev <interface> parent 1: classid 1:1 htb rate 10Gbit prio 2 quantum 409600
> +
> + # tc class add dev <interface> parent 1: classid 1:2 htb rate 10Gbit prio 2 quantum 188416
> +
> + # tc class add dev <interface> parent 1: classid 1:2 htb rate 10Gbit prio 2 quantum 32768
last two rules should presumably have different classids?
--
pw-bot: cr
next prev parent reply other threads:[~2023-07-19 2:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 9:33 [net-next Patch v3 0/4] octeontx2-pf: support Round Robin scheduling Hariprasad Kelam
2023-07-17 9:33 ` [net-next Patch v3 1/4] octeontx2-pf: implement transmit schedular allocation algorithm Hariprasad Kelam
2023-07-17 9:33 ` [net-next Patch v3 2/4] sch_htb: Allow HTB quantum parameter in offload mode Hariprasad Kelam
2023-07-17 9:33 ` [net-next Patch v3 3/4] octeontx2-pf: htb offload support for Round Robin scheduling Hariprasad Kelam
2023-07-17 9:33 ` [net-next Patch v3 4/4] docs: octeontx2: extend documentation " Hariprasad Kelam
2023-07-19 2:44 ` Jakub Kicinski [this message]
2023-07-19 10:11 ` [EXT] " Hariprasad Kelam
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=20230718194431.38c02846@kernel.org \
--to=kuba@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=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 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).