[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220414104259.0b928249@kernel.org>
Date: Thu, 14 Apr 2022 10:42:59 +0200
From: Jakub Kicinski <kuba@...nel.org>
To: Tan Tee Min <tee.min.tan@...ux.intel.com>
Cc: Richard Cochran <richardcochran@...il.com>,
Tan Tee Min <tee.min.tan@...el.com>,
Giuseppe Cavallaro <peppe.cavallaro@...com>,
Alexandre Torgue <alexandre.torgue@...com>,
Jose Abreu <joabreu@...opsys.com>,
"David S . Miller" <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Rayagond Kokatanur <rayagond@...avyalabs.com>,
netdev@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, Voon Wei Feng <weifeng.voon@...el.com>,
Wong Vee Khee <vee.khee.wong@...el.com>,
Song Yoong Siang <yoong.siang.song@...el.com>
Subject: Re: [PATCH net 1/1] net: stmmac: add fsleep() in HW Rx timestamp
checking loop
On Thu, 14 Apr 2022 15:29:34 +0800 Tan Tee Min wrote:
> > > --- a/drivers/net/ethernet/stmicro/stmmac/dwmac4_descs.c
> > > +++ b/drivers/net/ethernet/stmicro/stmmac/dwmac4_descs.c
> > > @@ -279,10 +279,11 @@ static int dwmac4_wrback_get_rx_timestamp_status(void *desc, void *next_desc,
> > > /* Check if timestamp is OK from context descriptor */
> > > do {
> > > ret = dwmac4_rx_check_timestamp(next_desc);
> > > - if (ret < 0)
> > > + if (ret <= 0)
> > > goto exit;
> > > i++;
> > >
> > > + fsleep(1);
> >
> > This is nutty. Why isn't this code using proper deferral mechanisms
> > like work or kthread?
>
> Appreciate your comment.
> The dwmac4_wrback_get_rx_timestamp_status() is called by stmmac_rx()
> function which is scheduled by NAPI framework.
> Do we still need to create deferred work inside NAPI work?
> Would you mind to explain it more in detail?
fsleep() is a big hammer, can you try cpu_relax() and bumping the max
loop count a little?
Powered by blists - more mailing lists