linearize skb with tiny unaligned fragent is back ?

Hallo,

really nice to see I can use my very old goflex-net / -home and docstar with an actual kernel ! (Thank you very much !)
What I did:
1.) Download your file for linux-6.10.11 ....
2.) untar linux-6.10.11.tar.xz from kernel.org and use your patch file + config
3.) Use 6.10.11-12, 6.10.12-13, 6.10.13-14 patches from kernel.org
4.) Build the entire with make bindeb-pkg ....

First of all, the system is booting, everything seems to just work (bullseye file server) ...
But the speed of samba + nfs was really unknown worse, because system-journal writes with high speed the
error: mv643xx_eth_port.0 eth0: failed to linearize skb with tiny unaligned fragment
almost all the time !
Setting ethtool - K eth0 tso off "solve" this for now, but it isn't a real solution ...

Bye

Bernd Oelker,

> First of all, the system is booting, everything
> seems to just work (bullseye file server) ...
> But the speed of samba + nfs was really unknown
> worse, because system-journal writes with high
> speed the
> error: mv643xx_eth_port.0 eth0: failed to
> linearize skb with tiny unaligned fragment
> almost all the time !
> Setting ethtool - K eth0 tso off "solve" this for
> now, but it isn't a real solution ...
>

1. Have you check the network speed by itself by running iperf?

See some some benchmark and tuning in the Wiki thread

Quote

Perfornance Tuning & Benchmarks

Pogo ProV3 vs Pogo E02
Another Pogo Pro V3 benchmarks
Network performance - SAMBA - NFS (various protocols)
Pogo Pro V3 Network NFS benchmarks
Kirkwood vs OXNAS network performance (with flow control)
Kirkwood vs OXNAS network performance (flow control turned off )
OXNAS vs OXNAS network performance (flow control turned off)
Network Benchmarks for Thecus N2350 (Armada 385) and Zyxel NSA325 (Kirkwood 6820)
Network Benchmarks for Zyxel NSA310S (Kirkwood 6281) and GTI Mirabox (Armada 370)
Samba Tuning
Mount NTFS with big_writes
Increase NFSD max_block_size
Reduce NFSD threads

May be "Increase NFSD max_block_size" will help.

2. Also try running kernel linux-6.9.6-kirkwood-tld-1

Quote
https://forum.doozan.com/read.php?2,12096
Updated 26 Jun 2024:

Kernel linux-6.9.6-kirkwood-tld-1 package has been uploaded.

The GoFlex Net/Home network card (same as other Kirkwood boxes) is running with flow control off and TSO on.

I have been running 2 GoFlex Home as media servers (using both NFS and Samba). I have not seen this problem. But they are running older kernels. I think I will upgrade the kernel on these boxes and see if anything strange happens.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Now I recalled that this is an old kernel bug which showed up in low RAM boards. I thought the kernel has fixed it. Perhaps it's not totally fixed and now coming back.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Also see this

Tuning for low RAM boxes

https://forum.doozan.com/read.php?2,116309,116324#msg-116324

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Okay,

Kernel-6-10.14-kirkwood-tld-1 :
iperf3 -c =>
Connecting to host 172.30.30.9, port 5201
[ 5] local 172.30.30.32 port 43380 connected to 172.30.30.9 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.01 sec 109 MBytes 902 Mbits/sec 0 518 KBytes
[ 5] 1.01-2.01 sec 105 MBytes 884 Mbits/sec 0 518 KBytes
[ 5] 2.01-3.01 sec 106 MBytes 887 Mbits/sec 0 518 KBytes
[ 5] 3.01-4.00 sec 105 MBytes 887 Mbits/sec 0 518 KBytes
[ 5] 4.00-5.00 sec 105 MBytes 884 Mbits/sec 0 518 KBytes
[ 5] 5.00-6.01 sec 108 MBytes 892 Mbits/sec 0 518 KBytes
[ 5] 6.01-7.00 sec 105 MBytes 890 Mbits/sec 0 518 KBytes
[ 5] 7.00-8.00 sec 106 MBytes 890 Mbits/sec 0 518 KBytes
[ 5] 8.00-9.00 sec 106 MBytes 892 Mbits/sec 0 518 KBytes
[ 5] 9.00-10.00 sec 106 MBytes 890 Mbits/sec 0 518 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.04 GBytes 890 Mbits/sec 0 sender
[ 5] 0.00-10.01 sec 1.04 GBytes 889 Mbits/sec receiver

root@goflex:~# iperf3 -s
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 172.30.30.172, port 39738
[ 5] local 172.30.30.32 port 5201 connected to 172.30.30.172 port 39742
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 62.8 MBytes 526 Mbits/sec
[ 5] 1.00-2.00 sec 64.6 MBytes 542 Mbits/sec
[ 5] 2.00-3.01 sec 65.5 MBytes 548 Mbits/sec
[ 5] 3.01-4.00 sec 66.3 MBytes 559 Mbits/sec
[ 5] 4.00-5.00 sec 65.1 MBytes 545 Mbits/sec
[ 5] 5.00-6.01 sec 64.3 MBytes 539 Mbits/sec
[ 5] 6.01-7.00 sec 65.2 MBytes 549 Mbits/sec
[ 5] 7.00-8.00 sec 64.7 MBytes 542 Mbits/sec
[ 5] 8.00-9.00 sec 62.5 MBytes 524 Mbits/sec
[ 5] 9.00-10.00 sec 65.3 MBytes 547 Mbits/sec
[ 5] 10.00-10.04 sec 2.00 MBytes 512 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.04 sec 648 MBytes 542 Mbits/sec receiver

When I test the same with dockstar, kernel 5.15.121-kirkwood-tld-1

Connecting to host 172.30.30.9, port 5201
[ 5] local 172.30.30.30 port 44442 connected to 172.30.30.9 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 112 MBytes 936 Mbits/sec 0 479 KBytes
[ 5] 1.00-2.00 sec 112 MBytes 941 Mbits/sec 0 479 KBytes
[ 5] 2.00-3.00 sec 112 MBytes 941 Mbits/sec 0 505 KBytes
[ 5] 3.00-4.00 sec 112 MBytes 940 Mbits/sec 0 530 KBytes
[ 5] 4.00-5.00 sec 112 MBytes 942 Mbits/sec 0 530 KBytes
[ 5] 5.00-6.01 sec 113 MBytes 942 Mbits/sec 0 530 KBytes
[ 5] 6.01-7.00 sec 112 MBytes 941 Mbits/sec 0 530 KBytes
[ 5] 7.00-8.00 sec 112 MBytes 942 Mbits/sec 0 530 KBytes
[ 5] 8.00-9.01 sec 113 MBytes 942 Mbits/sec 0 530 KBytes
[ 5] 9.01-10.00 sec 112 MBytes 941 Mbits/sec 0 530 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.10 GBytes 941 Mbits/sec 0 sender
[ 5] 0.00-10.01 sec 1.10 GBytes 940 Mbits/sec receiver

Accepted connection from 172.30.30.172, port 53486
[ 5] local 172.30.30.30 port 5201 connected to 172.30.30.172 port 60088
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 78.0 MBytes 652 Mbits/sec
[ 5] 1.00-2.00 sec 82.0 MBytes 689 Mbits/sec
[ 5] 2.00-3.00 sec 82.9 MBytes 695 Mbits/sec
[ 5] 3.00-4.00 sec 82.1 MBytes 690 Mbits/sec
[ 5] 4.00-5.00 sec 82.4 MBytes 690 Mbits/sec
[ 5] 5.00-6.00 sec 82.5 MBytes 691 Mbits/sec
[ 5] 6.00-7.00 sec 82.0 MBytes 689 Mbits/sec
[ 5] 7.00-8.00 sec 81.8 MBytes 687 Mbits/sec
[ 5] 8.00-9.00 sec 82.3 MBytes 689 Mbits/sec
[ 5] 9.00-10.00 sec 82.2 MBytes 688 Mbits/sec
[ 5] 10.00-10.04 sec 2.88 MBytes 684 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.04 sec 821 MBytes 686 Mbits/sec receiver

So, the older 5.15 kernel seems to be faster ....
I downloaded linux-6.9.9.tar.xz from kernel.org, put your linux-6.9.6-tld1 config in an use patch-6.9.6-tld ...
Building via nfs-chroot with odroid-XU4 => that takes time ....

This are the iperf3 values from GoFlexHome kernel 6.9.9-kirkwood-tld
=> There are almost the same than 6.10.14 ....
Connecting to host 172.30.30.9, port 5201
[ 5] local 172.30.30.32 port 58378 connected to 172.30.30.9 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.01 sec 94.5 MBytes 788 Mbits/sec 20 279 KBytes
[ 5] 1.01-2.01 sec 97.5 MBytes 815 Mbits/sec 0 279 KBytes
[ 5] 2.01-3.01 sec 97.5 MBytes 816 Mbits/sec 0 279 KBytes
[ 5] 3.01-4.00 sec 96.2 MBytes 817 Mbits/sec 0 279 KBytes
[ 5] 4.00-5.00 sec 97.5 MBytes 815 Mbits/sec 0 279 KBytes
[ 5] 5.00-6.01 sec 97.5 MBytes 815 Mbits/sec 0 279 KBytes
[ 5] 6.01-7.01 sec 96.2 MBytes 810 Mbits/sec 0 279 KBytes
[ 5] 7.01-8.01 sec 97.5 MBytes 815 Mbits/sec 0 279 KBytes
[ 5] 8.01-9.00 sec 96.2 MBytes 810 Mbits/sec 0 279 KBytes
[ 5] 9.00-10.00 sec 87.5 MBytes 738 Mbits/sec 0 279 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 958 MBytes 804 Mbits/sec 20 sender
[ 5] 0.00-10.01 sec 958 MBytes 803 Mbits/sec receiver

iperf Done.
root@goflex:~# iperf3 -s
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 172.30.30.9, port 44274
[ 5] local 172.30.30.32 port 5201 connected to 172.30.30.9 port 44278
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 66.0 MBytes 553 Mbits/sec
[ 5] 1.00-2.00 sec 66.0 MBytes 553 Mbits/sec
[ 5] 2.00-3.00 sec 65.9 MBytes 552 Mbits/sec
[ 5] 3.00-4.00 sec 66.4 MBytes 557 Mbits/sec
[ 5] 4.00-5.00 sec 66.4 MBytes 557 Mbits/sec
[ 5] 5.00-6.00 sec 66.0 MBytes 553 Mbits/sec
[ 5] 6.00-7.00 sec 65.5 MBytes 550 Mbits/sec
[ 5] 7.00-8.00 sec 66.5 MBytes 557 Mbits/sec
[ 5] 8.00-9.00 sec 66.2 MBytes 556 Mbits/sec
[ 5] 9.00-10.00 sec 66.0 MBytes 554 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.00 sec 661 MBytes 554 Mbits/sec receiver

Bernd Oelker,

It looks normal. The slower speed has a lot to do with the box on the other side, and the switch in the middle...

[ 5] local 172.30.30.32 port 5201 connected to 172.30.30.9 port 44278 
[ 5] 0.00-1.00 sec 66.0 MBytes 553 Mbits/sec

In any case, the issue here I think is with the low RAM and some other factors. Years ago, we had turned off TSO because of this bug, and then removed it because it seems to have been fixed in mainline.

On the GFNet, what's the output of

free -h
sysctl -a | grep swap
sysctl -a | grep vm.min_free_kbytes
ethtool eth0
ifconfig -a

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 10/22/2024 06:38PM by bodhi.