[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3adea6bbe1384e0ea6a06f4343d03ac2@realtek.com>
Date: Fri, 16 Aug 2024 07:50:45 +0000
From: Justin Lai <justinlai0215@...ltek.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com"
<edumazet@...gle.com>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"andrew@...n.ch"
<andrew@...n.ch>,
"jiri@...nulli.us" <jiri@...nulli.us>,
"horms@...nel.org"
<horms@...nel.org>,
"rkannoth@...vell.com" <rkannoth@...vell.com>,
"jdamato@...tly.com" <jdamato@...tly.com>,
Ping-Ke Shih <pkshih@...ltek.com>, Larry Chiu <larry.chiu@...ltek.com>
Subject: RE: [PATCH net-next v27 07/13] rtase: Implement a function to receive packets
> On Mon, 12 Aug 2024 14:35:33 +0800 Justin Lai wrote:
> > + if (!delta && workdone)
> > + netdev_info(dev, "no Rx buffer allocated\n");
> > +
> > + ring->dirty_idx += delta;
> > +
> > + if ((ring->dirty_idx + RTASE_NUM_DESC) == ring->cur_idx)
> > + netdev_emerg(dev, "Rx buffers exhausted\n");
>
> Memory allocation failures happen, we shouldn't risk spamming the logs.
> I mean these two messages and the one in rtase_alloc_rx_data_buf(), the
> should be removed.
>
> There is a alloc_fail statistic defined in include/net/netdev_queues.h that's the
> correct way to report buffer allocation failures.
> And you should have a periodic service task / work which checks for buffers
> being exhausted, and if they are schedule NAPI so that it tries to allocate.
Hi Jakub,
Thank you for the comments you provided. I will modify it.
Thanks
Justin
Powered by blists - more mailing lists