[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+sq2CdkfuMWE4jf0QEQc4w-2Nb45nER64BV8EbSroJcYi=__Q@mail.gmail.com>
Date: Mon, 12 Jun 2023 23:53:06 +0530
From: Sunil Kovvuri <sunil.kovvuri@...il.com>
To: Vladimir Oltean <olteanv@...il.com>
Cc: Alexis Lothoré <alexis.lothore@...tlin.com>,
Andrew Lunn <andrew@...n.ch>, Florian Fainelli <f.fainelli@...il.com>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, Thomas Petazzoni <thomas.petazzoni@...tlin.com>, paul.arola@...us.com,
scott.roberts@...us.com
Subject: Re: [PATCH net-next 2/2] net: dsa: mv88e6xxx: implement egress tbf
qdisc for 6393x family
On Mon, Jun 12, 2023 at 3:13 PM Vladimir Oltean <olteanv@...il.com> wrote:
>
> Hi Sunil,
>
> On Mon, Jun 12, 2023 at 12:04:56PM +0530, Sunil Kovvuri wrote:
> > For setting up simple per-port ratelimit, instead of TBF isn't "egress
> > matchall" suitable here ?
>
> "matchall" is a filter. What would be the associated action for a
> port-level shaper?
As Alexis mentioned I was referring to "matchall + policer".
Thanks,
Sunil.
Powered by blists - more mailing lists