From: Claudiu Manoil <claudiu.manoil@nxp.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>
Cc: Richie Pearn <richard.pearn@nxp.com>,
Camelia Alexandra Groza <camelia.groza@nxp.com>,
Po Liu <po.liu@nxp.com>
Subject: RE: [PATCH net] net: enetc: make sure all traffic classes can send large frames
Date: Thu, 21 Oct 2021 09:37:21 +0000 [thread overview]
Message-ID: <DB9PR04MB8395E7370B07F8D36B10026896BF9@DB9PR04MB8395.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20211020173340.1089992-1-vladimir.oltean@nxp.com>
> -----Original Message-----
> From: Vladimir Oltean <vladimir.oltean@nxp.com>
> Sent: Wednesday, October 20, 2021 8:34 PM
[...]
> Subject: [PATCH net] net: enetc: make sure all traffic classes can send large
> frames
>
> The enetc driver does not implement .ndo_change_mtu, instead it
> configures the MAC register field PTC{Traffic Class}MSDUR[MAXSDU]
> statically to a large value during probe time.
>
> The driver used to configure only the max SDU for traffic class 0, and
> that was fine while the driver could only use traffic class 0. But with
> the introduction of mqprio, sending a large frame into any other TC than
> 0 is broken.
>
> This patch fixes that by replicating per traffic class the static
> configuration done in enetc_configure_port_mac().
>
> Fixes: cbe9e835946f ("enetc: Enable TC offloading with mqprio")
> Reported-by: Richie Pearn <richard.pearn@nxp.com>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
> ---
Reviewed-by: <Claudiu Manoil <claudiu.manoil@nxp.com>
next prev parent reply other threads:[~2021-10-21 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 17:33 [PATCH net] net: enetc: make sure all traffic classes can send large frames Vladimir Oltean
2021-10-21 9:37 ` Claudiu Manoil [this message]
2021-10-21 15:10 ` patchwork-bot+netdevbpf
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=DB9PR04MB8395E7370B07F8D36B10026896BF9@DB9PR04MB8395.eurprd04.prod.outlook.com \
--to=claudiu.manoil@nxp.com \
--cc=camelia.groza@nxp.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=po.liu@nxp.com \
--cc=richard.pearn@nxp.com \
--cc=vladimir.oltean@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 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.