ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log http://irclog.whitequark.org/linux-rockchip | Community GH https://github.com/linux-rockchip | Rockchip GH https://github.com/rockchip-linux | ML https://groups.google.com/group/linux-rockchip
dmnq has joined #linux-rockchip
dmnq has quit [Remote host closed the connection]
dmnq has joined #linux-rockchip
dmnq has quit [Remote host closed the connection]
dmnq has joined #linux-rockchip
dmnq has quit [Remote host closed the connection]
dmnq has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
dmnq has quit [Remote host closed the connection]
dmnq has joined #linux-rockchip
dmnq has quit [Remote host closed the connection]
dmnq has joined #linux-rockchip
dmnq has quit [Ping timeout: 272 seconds]
vstehle has quit [Ping timeout: 240 seconds]
field^Zzz3 has joined #linux-rockchip
field^Zzz2 has quit [Ping timeout: 240 seconds]
_whitelogger has joined #linux-rockchip
dmnq has joined #linux-rockchip
nashpa has quit [Ping timeout: 272 seconds]
dmnq has quit [Ping timeout: 268 seconds]
nashpa has joined #linux-rockchip
dmnq has joined #linux-rockchip
dmnq_ has joined #linux-rockchip
dmnq_ has quit [Remote host closed the connection]
dmnq_ has joined #linux-rockchip
dmnq_ has quit [Ping timeout: 250 seconds]
vagrantc has joined #linux-rockchip
vstehle has joined #linux-rockchip
dmnq_ has joined #linux-rockchip
dmnq_ has quit []
aalm has quit [Read error: Connection reset by peer]
guthwine has quit [Remote host closed the connection]
guthwine has joined #linux-rockchip
<guthwine> mmind00: posted some stuff here: https://paste.debian.net/hidden/dbdaa5d1
vagrantc has quit [Quit: leaving]
hanetzer has quit [Remote host closed the connection]
hanetzer has joined #linux-rockchip
guthwine has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
scelestic has joined #linux-rockchip
vagrantc has joined #linux-rockchip
BenG83 has quit [Ping timeout: 250 seconds]
stikonas has quit [Remote host closed the connection]
<vagrantc> beeble: so, finally got arm-trusted-firmware into debian ... still have any plans to get puma-rk3399 working with upstream atf?
somy has joined #linux-rockchip
vagrantc has quit [Ping timeout: 260 seconds]
vicencb has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
aalm has joined #linux-rockchip
ayaka has quit [Read error: Connection reset by peer]
ayaka has joined #linux-rockchip
vagrantc has joined #linux-rockchip
vagrantc has quit [Remote host closed the connection]
vagrantc has joined #linux-rockchip
<quark_> anyone noticed that if "tx-checksum-ipv6: on" ipv6 transmit performance is very poor? happens at least with rk3399
stikonas has joined #linux-rockchip
<mmind00> quark_: maybe that checksumming is done in software?
<quark_> I mean very poor <1Mbits
<quark_> this might be mtu related. I just running test with reduced mtu
<mmind00> quark_: no idea ... i.e. on my rk3399-firefly I got decent rates on an ssh transfer recently (like >10MB/sec)
<mmind00> but that is all IPv4
<quark_> yup. just tested with MTU 1498. ipv6 transmit is ok when "tx-checksum-ipv6: on"
<quark_> there is no problem with IPv4 and tx-checksums
<quark_> ipv6 with MTU 1498 iperf3 send
<quark_> [ ID] Interval Transfer Bitrate Retr
<quark_> [ 5] 0.00-10.00 sec 1.08 GBytes 928 Mbits/sec 1 sender
<quark_> [ 5] 0.00-10.03 sec 1.08 GBytes 923 Mbits/sec receiver
<quark_> and with mtu > 1498
<quark_> [ ID] Interval Transfer Bitrate Retr
<quark_> [ 5] 0.00-10.00 sec 83.7 KBytes 68.5 Kbits/sec 16 sender
<quark_> [ 5] 0.00-10.04 sec 19.5 KBytes 15.9 Kbits/sec receiver
<quark_> MTU 1500 and "tx-checksum-ipv6: off" then I get almost 1Gbits with ipv6
<quark_> hmm. If I set iperf3 maximum segment size to 1438 ipv6 transmit works perfectly. so somehow this is packet size related
vagrantc has quit [Quit: leaving]
<stikonas> there are IPv6 checksumming problems with rockpro64 too
<stikonas> quark_: I disable it in the dts with the patch
<stikonas> so it's not board specific
<quark_> stikonas: have to tried to reduce mtu or run iperf3 with "-M 1438" option?
<stikonas> quark_: no, I only tried tx-checksum-ipv6: off
<stikonas> I suppose it will help just like it helped you
<stikonas> I'll recompile my kernel to test...
<quark_> I'm trying to make raw capture of network packets. it seems that linux kernel does ipv6 fragmentation even when you just tcpdump packets from interface
JohnDoe_71Rus has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
sb35 has joined #linux-rockchip
sb35 has quit [Ping timeout: 250 seconds]
<stikonas> quark_: indeed, I added MTUBytes=1438 to my systemd-networkd config and now iperf5 shows about 925 Mbit
<stikonas> quark_: I didn't realize you are the same person I emailed :D
sb35 has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
<stikonas> quark_: even with lower MTU, somehow my rockpro64 is quite unstable unless I disable tx checksums...
<stikonas> althouth iperf3 performance was higher...
<stikonas> s/althouth/although/
ldevulder has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
ldevulder has quit [Ping timeout: 240 seconds]
stikonas has quit [Remote host closed the connection]