From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: <wei.fang@nxp.com>
Cc: <claudiu.manoil@nxp.com>, <vladimir.oltean@nxp.com>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] net: enetc: correct the indexes of highest and 2nd highest TCs
Date: Tue, 6 Jun 2023 21:41:57 +0200 [thread overview]
Message-ID: <ZH+MBdlRAybwqFo8@boxer> (raw)
In-Reply-To: <20230606084618.1126471-1-wei.fang@nxp.com>
On Tue, Jun 06, 2023 at 04:46:18PM +0800, wei.fang@nxp.com wrote:
> From: Wei Fang <wei.fang@nxp.com>
if you are a sender then you could skip line above.
>
> For ENETC hardware, the TCs are numbered from 0 to N-1, where N
> is the number of TCs. Numerically higher TC has higher priority.
> It's obvious that the highest priority TC index should be N-1 and
> the 2nd highest priority TC index should be N-2.
> However, the previous logic uses netdev_get_prio_tc_map() to get
> the indexes of highest priority and 2nd highest priority TCs, it
> does not make sense and is incorrect. It may get wrong indexes of
> the two TCs and make the CBS unconfigurable. e.g.
> $ tc qdisc add dev eno0 parent root handle 100: mqprio num_tc 6 \
> map 0 0 1 1 2 3 4 5 queues 1@0 1@1 1@2 1@3 2@4 2@6 hw 1
> $ tc qdisc replace dev eno0 parent 100:6 cbs idleslope 100000 \
> sendslope -900000 hicredit 12 locredit -113 offload 1
> $ Error: Specified device failed to setup cbs hardware offload.
> ^^^^^
newlines between commit message and example output would improve
readability. tc commands are awful to read by themselves :P
Please describe in the commit message what is the actual fix.
>
> Fixes: c431047c4efe ("enetc: add support Credit Based Shaper(CBS) for hardware offload")
> Signed-off-by: Wei Fang <wei.fang@nxp.com>
> ---
> drivers/net/ethernet/freescale/enetc/enetc_qos.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/freescale/enetc/enetc_qos.c b/drivers/net/ethernet/freescale/enetc/enetc_qos.c
> index 83c27bbbc6ed..126007ab70f6 100644
> --- a/drivers/net/ethernet/freescale/enetc/enetc_qos.c
> +++ b/drivers/net/ethernet/freescale/enetc/enetc_qos.c
> @@ -181,8 +181,8 @@ int enetc_setup_tc_cbs(struct net_device *ndev, void *type_data)
> int bw_sum = 0;
> u8 bw;
>
> - prio_top = netdev_get_prio_tc_map(ndev, tc_nums - 1);
> - prio_next = netdev_get_prio_tc_map(ndev, tc_nums - 2);
> + prio_top = tc_nums - 1;
> + prio_next = tc_nums - 2;
>
> /* Support highest prio and second prio tc in cbs mode */
> if (tc != prio_top && tc != prio_next)
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2023-06-06 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 8:46 [PATCH net] net: enetc: correct the indexes of highest and 2nd highest TCs wei.fang
2023-06-06 9:16 ` Vladimir Oltean
2023-06-07 2:02 ` Wei Fang
2023-06-06 19:41 ` Maciej Fijalkowski [this message]
2023-06-06 21:13 ` Jakub Kicinski
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=ZH+MBdlRAybwqFo8@boxer \
--to=maciej.fijalkowski@intel.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.com \
--cc=wei.fang@nxp.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