[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220511231745.4olqfvxiz4qm5oht@skbuf>
Date: Wed, 11 May 2022 23:17:46 +0000
From: Vladimir Oltean <vladimir.oltean@....com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>,
Eric Dumazet <edumazet@...gle.com>,
Claudiu Manoil <claudiu.manoil@....com>,
Vinicius Costa Gomes <vinicius.gomes@...el.com>,
Michael Walle <michael@...le.cc>,
Xiaoliang Yang <xiaoliang.yang_1@....com>,
Po Liu <po.liu@....com>
Subject: Re: [PATCH net-next 2/2] net: enetc: count the tc-taprio window drops
On Wed, May 11, 2022 at 04:13:46PM -0700, Jakub Kicinski wrote:
> On Wed, 11 May 2022 22:57:46 +0000 Vladimir Oltean wrote:
> > The only entry that is a counter in the Scheduled Traffic MIB is TransmissionOverrun,
> > but that isn't what this is. Instead, this would be a TransmissionOverrunAvoidedByDropping,
> > for which there appears to be no standardization.
>
> TransmissionOversized? There's no standardization in terms of IEEE but
> the semantics seem pretty clear right? The packet is longer than the
> entire window so it can never go out?
Yes, so what are you saying? Become the ad-hoc standards body for
scheduled traffic?
Powered by blists - more mailing lists