[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48d03f3134bf49c0b04b34464cd7487b@realtek.com>
Date: Tue, 5 Sep 2023 10:37:45 +0000
From: Hayes Wang <hayeswang@...ltek.com>
To: Paolo Abeni <pabeni@...hat.com>, "kuba@...nel.org" <kuba@...nel.org>,
"davem@...emloft.net" <davem@...emloft.net>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
nic_swsd
<nic_swsd@...ltek.com>,
"linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>,
"linux-usb@...r.kernel.org"
<linux-usb@...r.kernel.org>
Subject: RE: [PATCH net] r8152: avoid the driver drops a lot of packets
Paolo Abeni <pabeni@...hat.com>
> Sent: Tuesday, September 5, 2023 6:11 PM
[...]
> > - /* limit the skb numbers for rx_queue */
> > - if (unlikely(skb_queue_len(&tp->rx_queue) >=
> 1000))
> > - break;
> > -
>
> Dropping this check looks dangerous to me. What if pause frames are
> disabled on the other end or dropped? It looks like this would cause
> unlimited memory consumption?!?
When the driver stops submitting rx, the driver wouldn't get any packet
from the device after the previous urbs which have been submitted return.
That is, skb_queue_len(&tp->rx_queue) wouldn't increase any more until
the driver starts submitting rx again.
Now, the driver stops submitting rx when the skb_queue_len more than 256,
so the check becomes redundant. The skb_queue_len has been limited less
than 1000.
Besides, if the flow control is disabled, the packets may be dropped by
the hardware when the FIFO of the device is full, after the driver stops
submitting rx.
Best Regards,
Hayes
Powered by blists - more mailing lists