[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250716140926.3aa10894@kernel.org>
Date: Wed, 16 Jul 2025 14:09:26 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Parvathi Pudi <parvathi@...thit.com>
Cc: danishanwar <danishanwar@...com>, rogerq <rogerq@...nel.org>,
andrew+netdev <andrew+netdev@...n.ch>, davem <davem@...emloft.net>,
edumazet <edumazet@...gle.com>, pabeni <pabeni@...hat.com>, robh
<robh@...nel.org>, krzk+dt <krzk+dt@...nel.org>, conor+dt
<conor+dt@...nel.org>, ssantosh <ssantosh@...nel.org>, richardcochran
<richardcochran@...il.com>, s hauer <s.hauer@...gutronix.de>, m-karicheri2
<m-karicheri2@...com>, glaroque <glaroque@...libre.com>, afd <afd@...com>,
saikrishnag <saikrishnag@...vell.com>, m-malladi <m-malladi@...com>, jacob
e keller <jacob.e.keller@...el.com>, diogo ivo <diogo.ivo@...mens.com>,
javier carrasco cruz <javier.carrasco.cruz@...il.com>, horms
<horms@...nel.org>, s-anna <s-anna@...com>, basharath
<basharath@...thit.com>, linux-arm-kernel
<linux-arm-kernel@...ts.infradead.org>, netdev <netdev@...r.kernel.org>,
devicetree <devicetree@...r.kernel.org>, linux-kernel
<linux-kernel@...r.kernel.org>, Vadim Fedorenko
<vadim.fedorenko@...ux.dev>, pratheesh <pratheesh@...com>, Prajith
Jayarajan <prajith@...com>, Vignesh Raghavendra <vigneshr@...com>, praneeth
<praneeth@...com>, srk <srk@...com>, rogerq <rogerq@...com>, krishna
<krishna@...thit.com>, pmohan <pmohan@...thit.com>, mohan
<mohan@...thit.com>
Subject: Re: [PATCH net-next v10 04/11] net: ti: prueth: Adds link
detection, RX and TX support.
On Wed, 16 Jul 2025 18:41:11 +0530 (IST) Parvathi Pudi wrote:
> >> Something needs to stop the queue, right? Otherwise the stack will
> >> send the frame right back to the driver.
> >
> > Yes, we will notify upper layer with “netif_tx_stop_queue()” when returning
> > “NETDEV_TX_BUSY” to not push again immediately.
>
> We reviewed the flow and found that the reason for NETDEV_TX_BUSY being
> notified to the upper layers is due lack of support for reliably detecting
> the TX completion event.
>
> In case of ICSSM PRU Ethernet, we do not have support for TX complete
> notification back to the driver from firmware and its like store and
> forget approach. So it will be tricky to enable back/resume the queue
> if we stop it when we see busy status.
IIUC this is all implemented in SW / FW. You either need to add
the notification or use a timer to unblock the queue.
Powered by blists - more mailing lists