[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ee1205d6-3d6b-447f-991e-903936d45ac7@redhat.com>
Date: Tue, 15 Oct 2024 13:57:07 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: Jijie Shao <shaojijie@...wei.com>, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org
Cc: shenjian15@...wei.com, wangpeiyang1@...wei.com, liuyonglong@...wei.com,
chenhao418@...wei.com, sudongming1@...wei.com, xujunsheng@...wei.com,
shiyongbang@...wei.com, libaihan@...wei.com, andrew@...n.ch,
jdamato@...tly.com, horms@...nel.org, kalesh-anakkur.purayil@...adcom.com,
christophe.jaillet@...adoo.fr, jonathan.cameron@...wei.com,
shameerali.kolothum.thodi@...wei.com, salil.mehta@...wei.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V12 net-next 07/10] net: hibmcge: Implement rx_poll
function to receive packets
On 10/15/24 13:41, Jijie Shao wrote:
> on 2024/10/15 18:28, Paolo Abeni wrote:
>> Side note: the above always uses the maximum MTU for the packet size,
>> if the device supports jumbo frames (8Kb size packets), it will
>> produce quite bad layout for the incoming packets... Is the device
>> able to use multiple buffers for the incoming packets?
>
> In fact, jumbo frames are not supported in device, and the maximum MTU is 4Kb.
FTR, even 4Kb is bad enough: tiny packets (tcp syn, UDP dns req) will
use a truesize above 5K. You can get a much better the layout using
copybreak.
Cheers,
Paolo
Powered by blists - more mailing lists