[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241217163538.GU780307@kernel.org>
Date: Tue, 17 Dec 2024 16:35:38 +0000
From: Simon Horman <horms@...nel.org>
To: Furong Xu <0x1207@...il.com>
Cc: netdev@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Jose Abreu <joabreu@...opsys.com>,
Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>, xfr@...look.com
Subject: Re: [PATCH net v1] net: stmmac: Drop useless code related to ethtool
rx-copybreak
On Tue, Dec 17, 2024 at 05:17:12PM +0800, Furong Xu wrote:
> After commit 2af6106ae949 ("net: stmmac: Introducing support for Page
> Pool"), these code turned to be useless and users of ethtool may get
> confused about the unhandled rx-copybreak parameter.
Hi Furong Xu,
I think it would be useful to explain why the change cited above
renders the copybreak implementation unnecessary.
>
> This patch mostly reverts
> commit 22ad38381547 ("stmmac: do not perform zero-copy for rx frames")
>
> Fixes: 2af6106ae949 ("net: stmmac: Introducing support for Page Pool")
Based on your description this feels more like an enhancement
for net-next, without a Fixes tag, than a fix for net.
> Signed-off-by: Furong Xu <0x1207@...il.com>
...
Powered by blists - more mailing lists