From: Simon Horman <simon.horman@corigine•com>
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
Subject: Re: [net-next Patch v6 1/6] sch_htb: Allow HTB priority parameter in offload mode
Date: Sat, 8 Apr 2023 18:22:31 +0200 [thread overview]
Message-ID: <ZDGUx586cnbyPa4M@corigine.com> (raw)
In-Reply-To: <20230406102103.19910-2-hkelam@marvell.com>
On Thu, Apr 06, 2023 at 03:50:58PM +0530, Hariprasad Kelam wrote:
> From: Naveen Mamindlapalli <naveenm@marvell•com>
>
> The current implementation of HTB offload returns the EINVAL error
> for unsupported parameters like prio and quantum. This patch removes
> the error returning checks for 'prio' parameter and populates its
> value to tc_htb_qopt_offload structure such that driver can use the
> same.
>
> Add prio parameter check in mlx5 driver, as mlx5 devices are not capable
> of supporting the prio parameter when htb offload is used. Report error
> if prio parameter is set to a non-default value.
>
> Signed-off-by: Naveen Mamindlapalli <naveenm@marvell•com>
> Co-developed-by: Rahul Rameshbabu <rrameshbabu@nvidia•com>
> Signed-off-by: Rahul Rameshbabu <rrameshbabu@nvidia•com>
> Signed-off-by: Hariprasad Kelam <hkelam@marvell•com>
> Signed-off-by: Sunil Kovvuri Goutham <sgoutham@marvell•com>
Reviewed-by: Simon Horman <simon.horman@corigine•com>
next prev parent reply other threads:[~2023-04-08 16:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 10:20 [net-next Patch v6 0/6] octeontx2-pf: HTB offload support Hariprasad Kelam
2023-04-06 10:20 ` [net-next Patch v6 1/6] sch_htb: Allow HTB priority parameter in offload mode Hariprasad Kelam
2023-04-08 16:22 ` Simon Horman [this message]
2023-04-06 10:20 ` [net-next Patch v6 2/6] octeontx2-pf: Rename tot_tx_queues to non_qos_queues Hariprasad Kelam
2023-04-06 10:21 ` [net-next Patch v6 3/6] octeontx2-pf: qos send queues management Hariprasad Kelam
2023-04-08 2:58 ` Jakub Kicinski
2023-04-06 10:21 ` [net-next Patch v6 4/6] octeontx2-pf: Refactor schedular queue alloc/free calls Hariprasad Kelam
2023-04-06 10:21 ` [net-next Patch v6 5/6] octeontx2-pf: Add support for HTB offload Hariprasad Kelam
2023-04-08 16:51 ` Simon Horman
2023-04-06 10:21 ` [net-next Patch v6 6/6] docs: octeontx2: Add Documentation for QOS 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=ZDGUx586cnbyPa4M@corigine.com \
--to=simon.horman@corigine$(echo .)com \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=gakula@marvell$(echo .)com \
--cc=hkelam@marvell$(echo .)com \
--cc=jerinj@marvell$(echo .)com \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=kuba@kernel$(echo .)org \
--cc=lcherian@marvell$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=maxtram95@gmail$(echo .)com \
--cc=naveenm@marvell$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=sbhatta@marvell$(echo .)com \
--cc=sgoutham@marvell$(echo .)com \
--cc=willemdebruijn.kernel@gmail$(echo .)com \
--cc=xiyou.wangcong@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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