I applied your patches from the 6.18-jumbo-refactor branch on top of Frank’s 6.18-jumbo branch (which I think is what you also used).
It seems this only happens when there is some use of the interface. In my case the interface was down, but I still had the vlans set up. When I remove all vlans, then down eth1 I changed the mtu without any issues. If I only down eth1 it still happened.
I never tested it with vlans before. Thanks for the feedback. I’ll check what I can do. Can you please provide the dmesg messages/ other outputs?
Thanks!
I double checked the mtk_eth_soc code against your branch and noticed there were a few differences. When I use exactly the code from your branch the system seems to work without issues up to now. It seems that the code differences caused the driver to release and reallocate the pools more often (i.e., on mtu change and link loss). I am not sure something else would cause a release/realloc of the pool, and if so it that would still cause issues. I’ll monitor for a while and report back if I see other issues.
Apologies for the confusion, somehow I missed the code differences the first time.
Throughput between various machines is fantastic, reaching 9-10 gbit consistently depending on the combination of machines (it seems a bit slower receiving from some Marvell based systems). With the previous 2022 bytes mtu limit it was never really exceeding 8.5, mostly around 7.8.
-Wilfried