From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Vinicius Costa Gomes <vinicius.gomes@intel.com>,
Michael Walle <michael@walle.cc>,
Xiaoliang Yang <xiaoliang.yang_1@nxp.com>,
Po Liu <po.liu@nxp.com>
Subject: Re: [PATCH net-next 2/2] net: enetc: count the tc-taprio window drops
Date: Wed, 11 May 2022 22:57:46 +0000 [thread overview]
Message-ID: <20220511225745.xgrhiaghckrcxdaj@skbuf> (raw)
In-Reply-To: <20220511152740.63883ddf@kernel.org>
On Wed, May 11, 2022 at 03:27:40PM -0700, Jakub Kicinski wrote:
> On Tue, 10 May 2022 19:36:15 +0300 Vladimir Oltean wrote:
> > From: Po Liu <Po.Liu@nxp.com>
> >
> > The enetc scheduler for IEEE 802.1Qbv has 2 options (depending on
> > PTGCR[TG_DROP_DISABLE]) when we attempt to send an oversized packet
> > which will never fit in its allotted time slot for its traffic class:
> > either block the entire port due to head-of-line blocking, or drop the
> > packet and set a bit in the writeback format of the transmit buffer
> > descriptor, allowing other packets to be sent.
> >
> > We obviously choose the second option in the driver, but we do not
> > detect the drop condition, so from the perspective of the network stack,
> > the packet is sent and no error counter is incremented.
> >
> > This change checks the writeback of the TX BD when tc-taprio is enabled,
> > and increments a specific ethtool statistics counter and a generic
> > "tx_dropped" counter in ndo_get_stats64.
>
> Is there no MIB attribute in the standard for such drops?
>
> The semantics seem petty implementation-independent can we put it into
> some structured ethtool stats instead?
My copy of IEEE 802.1Q-2018 talks about the following MIB table entries
in clause 17.2.22 Structure of the IEEE8021-ST-MIB:
ieee8021STMaxSDU subtree
ieee8021STMaxSDUTable
ieee8021STTrafficClass
ieee8021STMaxSDU
ieee8021TransmissionOverrun
ieee8021STParameters
ieee8021STParametersTable
ieee8021STGateEnabled
ieee8021STAdminGateStates
ieee8021STOperGateStates
ieee8021STAdminControlListLength
ieee8021STOperControlListLength
ieee8021STAdminControlList
ieee8021STOperControlList
ieee8021STAdminCycleTimeNumerator
ieee8021STAdminCycleTimeDenominator
ieee8021STOperCycleTimeNumerator
ieee8021STOperCycleTimeDenominator
ieee8021STAdminCycleTimeExtension
ieee8021STOperCycleTimeExtension
ieee8021STAdminBaseTime
ieee8021STOperBaseTime
ieee8021STConfigChange
ieee8021STConfigChangeTime
ieee8021STTickGranularity
ieee8021STCurrentTime
ieee802STConfigPending
ieee8021STSupportedListMax
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.
next prev parent reply other threads:[~2022-05-11 22:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 16:36 [PATCH net-next 0/2] Count tc-taprio window drops in enetc driver Vladimir Oltean
2022-05-10 16:36 ` [PATCH net-next 1/2] net: enetc: manage ENETC_F_QBV in priv->active_offloads only when enabled Vladimir Oltean
2022-05-11 8:17 ` Claudiu Manoil
2022-05-10 16:36 ` [PATCH net-next 2/2] net: enetc: count the tc-taprio window drops Vladimir Oltean
2022-05-11 8:17 ` Claudiu Manoil
2022-05-11 22:27 ` Jakub Kicinski
2022-05-11 22:57 ` Vladimir Oltean [this message]
2022-05-11 23:13 ` Jakub Kicinski
2022-05-11 23:17 ` Vladimir Oltean
2022-05-11 23:36 ` Jakub Kicinski
2022-05-12 0:20 ` Vladimir Oltean
2022-05-12 0:52 ` Jakub Kicinski
2022-05-12 0:00 ` [PATCH net-next 0/2] Count tc-taprio window drops in enetc driver patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2021-06-02 12:21 [PATCH net-next 0/2] Report tc-taprio window drops in NXP ENETC driver Vladimir Oltean
2021-06-02 12:21 ` [PATCH net-next 2/2] net: enetc: count the tc-taprio window drops Vladimir Oltean
2021-06-02 17:19 ` Jakub Kicinski
2021-06-02 17:59 ` Vladimir Oltean
2021-06-02 21:30 ` 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=20220511225745.xgrhiaghckrcxdaj@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=po.liu@nxp.com \
--cc=vinicius.gomes@intel.com \
--cc=xiaoliang.yang_1@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