The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "G Thomas, Rohan" <rohan.g.thomas@altera.com>
To: Jakub Kicinski <kuba@kernel.org>,
	Rohan G Thomas via B4 Relay
	<devnull+rohan.g.thomas.altera.com@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Matthew Gerlach <matthew.gerlach@altera.com>
Subject: Re: [PATCH net-next v2] net: stmmac: est: Drop frames causing HLBS error
Date: Thu, 18 Sep 2025 07:50:59 +0530	[thread overview]
Message-ID: <071bc895-b26b-4f78-91c7-fd6d53a11e11@altera.com> (raw)
In-Reply-To: <20250917153345.27598d55@kernel.org>

Hi Jakub,

Thanks for reviewing the patch.

On 9/18/2025 4:03 AM, Jakub Kicinski wrote:
> On Mon, 15 Sep 2025 16:22:14 +0800 Rohan G Thomas via B4 Relay wrote:
>> From: Rohan G Thomas <rohan.g.thomas@altera.com>
>>
>> Drop those frames causing HLBS error to avoid HLBS interrupt
>> flooding and netdev watchdog timeouts due to blocked packets.
>> Also add HLBS frame drops to taprio stats.
> 
> I think these should be two separate commits.

Sure, I will do in the next version.

> 
> Also are the HLBS and DFBS acronyms obvious to everyone who works
> on TSN?

Even though the term Head-Of-Line Blocking is obvious, the acronyms HLBS
and DFBS are from the dwmac and dwxgmac databooks.

HLBS => Head-Of-Line Blocking due to Scheduling
DFBS => Drop Frames causing Scheduling Error

I’ll expand these acronyms in the next version for clarity.

Best Regards,
Rohan

      reply	other threads:[~2025-09-18  2:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15  8:22 [PATCH net-next v2] net: stmmac: est: Drop frames causing HLBS error Rohan G Thomas via B4 Relay
2025-09-17 22:33 ` Jakub Kicinski
2025-09-18  2:20   ` G Thomas, Rohan [this message]

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=071bc895-b26b-4f78-91c7-fd6d53a11e11@altera.com \
    --to=rohan.g.thomas@altera.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devnull+rohan.g.thomas.altera.com@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=matthew.gerlach@altera.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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