From: "Alexis Lothoré" <alexis.lothore@bootlin.com>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
paul.arola@telus.com, scott.roberts@telus.com
Subject: Re: [PATCH net-next 2/2] net: dsa: mv88e6xxx: implement egress tbf qdisc for 6393x family
Date: Fri, 9 Jun 2023 18:27:36 +0200 [thread overview]
Message-ID: <2c11201b-9cb5-cbf1-a53b-559dd6ab331e@bootlin.com> (raw)
In-Reply-To: <20230609145727.qt6qvyoheepstpz7@skbuf>
Hello Vladimir, thanks for the feedback,
On 6/9/23 16:57, Vladimir Oltean wrote:
> On Fri, Jun 09, 2023 at 04:18:12PM +0200, alexis.lothore@bootlin.com wrote:
>> +int mv88e6393x_tbf_add(struct mv88e6xxx_chip *chip, int port,
>> + struct tc_tbf_qopt_offload_replace_params *replace_params)
>> +{
>> + int rate_kbps = DIV_ROUND_UP(replace_params->rate.rate_bytes_ps * 8, 1000);
>> + int overhead = DIV_ROUND_UP(replace_params->rate.overhead, 4);
>> + int rate_step, decrement_rate, err;
>> + u16 val;
>> +
>> + if (rate_kbps < MV88E6393X_PORT_EGRESS_RATE_MIN_KBPS ||
>> + rate_kbps >= MV88E6393X_PORT_EGRESS_RATE_MAX_KBPS)
>> + return -EOPNOTSUPP;
>> +
>> + if (replace_params->rate.overhead > MV88E6393X_PORT_EGRESS_MAX_OVERHEAD)
>> + return -EOPNOTSUPP;
>
> How does tbf react to the driver returning -EOPNOTSUPP? I see tbf_offload_change()
> returns void and doesn't check the ndo_setup_tc() return code.
>
> Should we resolve that so that the error code is propagated to the user?
Indeed, checking some other TC Qdisc, some reports ndo_setup_tc errors (htb,
taprio, ...) to caller, some others do not (red, ets...). I can give it a try
and see the impact
>
> Also, it would be nice to extend struct tc_tbf_qopt_offload with a
> netlink extack, for the driver to state exactly the reason for the
> offload failure.
ACK, I will add the extack struct
>
> Not sure if EOPNOTSUPP is the return code to use here for range checks,
> rather than ERANGE.
I was not sure about proper error codes on all those checks. Since all those
errors are about what hardware can handle/can not handle, I felt like EOPNOTSUPP
was the most relevant one. But indeed it may make more sense for user to get
ERANGE here, I will update accordingly
>> +
>> + /* Switch supports only max rate configuration. There is no
>> + * configurable burst/max size nor latency.
>> + * Formula defining registers value is:
>> + * EgressRate = 8 * EgressDec / (16ns * desired Rate)
>> + * EgressRate is a set of fixed values depending of targeted range
>> + */
>> + if (rate_kbps < MBPS_TO_KBPS(1)) {
>> + decrement_rate = rate_kbps / 64;
>> + rate_step = MV88E6XXX_PORT_EGRESS_RATE_CTL1_STEP_64_KBPS;
>> + } else if (rate_kbps < MBPS_TO_KBPS(100)) {
>> + decrement_rate = rate_kbps / MBPS_TO_KBPS(1);
>> + rate_step = MV88E6XXX_PORT_EGRESS_RATE_CTL1_STEP_1_MBPS;
>> + } else if (rate_kbps < GBPS_TO_KBPS(1)) {
>> + decrement_rate = rate_kbps / MBPS_TO_KBPS(10);
>> + rate_step = MV88E6XXX_PORT_EGRESS_RATE_CTL1_STEP_10_MBPS;
>> + } else {
>> + decrement_rate = rate_kbps / MBPS_TO_KBPS(100);
>> + rate_step = MV88E6XXX_PORT_EGRESS_RATE_CTL1_STEP_100_MBPS;
>> + }
>> +
>> + dev_dbg(chip->dev, "p%d: adding egress tbf qdisc with %dkbps rate",
>> + port, rate_kbps);
>> + val = decrement_rate;
>> + val |= (overhead << MV88E6XXX_PORT_EGRESS_RATE_CTL1_FRAME_OVERHEAD_SHIFT);
>> + err = mv88e6xxx_port_write(chip, port, MV88E6XXX_PORT_EGRESS_RATE_CTL1,
>> + val);
>> + if (err)
>> + return err;
>> +
>> + val = rate_step;
>> + /* Configure mode to bits per second mode, on layer 1 */
>> + val |= MV88E6XXX_PORT_EGRESS_RATE_CTL2_COUNT_L1_BYTES;
>> + err = mv88e6xxx_port_write(chip, port, MV88E6XXX_PORT_EGRESS_RATE_CTL2,
>> + val);
>> + if (err)
>> + return err;
>> +
>> + return 0;
>> +}
>> +
>> +int mv88e6393x_tbf_del(struct mv88e6xxx_chip *chip, int port)
>> +{
>> + int err;
>> +
>> + dev_dbg(chip->dev, "p%d: removing tbf qdisc", port);
>> + err = mv88e6xxx_port_write(chip, port, MV88E6XXX_PORT_EGRESS_RATE_CTL2,
>> + 0x0000);
>> + if (err)
>> + return err;
>> + return mv88e6xxx_port_write(chip, port, MV88E6XXX_PORT_EGRESS_RATE_CTL1,
>> + 0x0001);
>
> I guess this should return void and proceed on errors, rather than exit early.
> Maybe shout out loud that things went wrong.
ACK
>
>> +}
>> +
>> +static int mv88e6393x_tc_setup_qdisc_tbf(struct mv88e6xxx_chip *chip, int port,
>> + struct tc_tbf_qopt_offload *qopt)
>> +{
>> + /* Device only supports per-port egress rate limiting */
>> + if (qopt->parent != TC_H_ROOT)
>> + return -EOPNOTSUPP;
>> +
>> + switch (qopt->command) {
>> + case TC_TBF_REPLACE:
>> + return mv88e6393x_tbf_add(chip, port, &qopt->replace_params);
>> + case TC_TBF_DESTROY:
>> + return mv88e6393x_tbf_del(chip, port);
>> + default:
>> + return -EOPNOTSUPP;
>> + }
>> +
>> + return -EOPNOTSUPP;
>> +}
--
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-06-09 16:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 14:18 [PATCH net-next 0/2] add egress rate limit offload for Marvell 6393X family alexis.lothore
2023-06-09 14:18 ` [PATCH net-next 1/2] net: dsa: mv88e6xxx: allow driver to hook TC callback alexis.lothore
2023-06-09 14:18 ` [PATCH net-next 2/2] net: dsa: mv88e6xxx: implement egress tbf qdisc for 6393x family alexis.lothore
2023-06-09 14:53 ` Andrew Lunn
2023-06-09 16:27 ` Alexis Lothoré
2023-06-09 17:16 ` Andrew Lunn
2023-06-09 17:38 ` Alexis Lothoré
[not found] ` <CA+sq2CcG4pQDLcw+fTkcEfTZv6zPY3pcGCKeOy8owiaRF2HELA@mail.gmail.com>
2023-06-12 8:54 ` Alexis Lothoré
2023-06-12 9:43 ` Vladimir Oltean
2023-06-12 18:23 ` Sunil Kovvuri
2023-06-12 18:51 ` Vladimir Oltean
2023-06-09 14:57 ` Vladimir Oltean
2023-06-09 16:27 ` Alexis Lothoré [this message]
2023-06-09 15:52 ` kernel test robot
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=2c11201b-9cb5-cbf1-a53b-559dd6ab331e@bootlin.com \
--to=alexis.lothore@bootlin.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=paul.arola@telus.com \
--cc=scott.roberts@telus.com \
--cc=thomas.petazzoni@bootlin.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