Just few first minute impressions on QNAP after the merge.
First I returned completely to 1G memory profile and Auto for pbuf.
I don't see any of this on QNAP.
I have full Gigabit speeds on LAN and WLAN without any limits and zero CPU.
Even more, now when torrents run in background I am still able to get the full 1G LAN/WLAN speeds.
Before I was able to reach ~800-850Mbps at most when torrents were background tasking. Without torrents running I was able to get 1G.
Available memory is more even with torrents running for the first hour usage but let it run for at least several hours/days and see.
A few other mainly cosmetic glitches.
Status -> Processes page is empty as it was before too.
Nlbwmon doesn't work either (maybe it's outdated now). I'm not sure it is really necessary. This is just for information, maybe others observed the same behaviour.
I still find it somewhat useful for statistics on older ipq806x NSS builds (R7800 w/ 23.05 NSS)
Edit - @qosmio What branch should I use now to compile NSS-wifi or NSS-wifi-skb?
Lastly I used default NSS-wifi. Maybe I was wrong about the merge and I should use NSS-wifi-skb now to use memory recycle feature?
Edit 2 (Important clarification) - Seems that I've compiled this build before skb was pushed to the NSS wifi branch. So take all of the data here only as a reference and to compare the NSS build performance right before the skb introduction.
NOTE: Now I am only compiling for the AX3600, AX6 and AX9000 and Dynalink DL-WRX36 and Buffalo WXR-5950AX12 and QNAP QHora-301W devices and Netgear RAX120v2, if anyone has used my versions with other devices, tell me and I will add them again.
NOTE: Now I am only compiling for the AX3600, AX6 and AX9000 and Dynalink DL-WRX36 and Buffalo WXR-5950AX12 and QNAP QHora-301W devices and Netgear RAX120v2, if anyone has used my versions with other devices, tell me and I will add them again.
I remember you had issues with 10G_1 port and uniphy autoneg time out! some time ago. I suppose you use the MBN 10G FW loaded from U-Boot.
Have you tried to use the stock QNAP 10G FW loaded from NVMEM on your qsdk backports version and see how it goes.
Yes, I read that and understood it. I'm glad you have no issues with qnap.
I was just asking about the 10G Firmware and the recent commit - qualcommax: 301w: enable using kernel for AQR firmware loading.
At least because you use your own NSS build and obviously the recent NSS builds probably require additional patch for the 10G_1 port to work properly with stock 10G FW.
Obviously a patch is needed to mitigate the uniphy autoneg time out! in syslog.
Lastly I tested with 2.5G mode, but same not working.
nss-dp 3a001800.dp5 10g-1: PHY Link up speed: 2500
br-lan: port 1(10g-1) entered blocking state
br-lan: port 1(10g-1) entered forwarding state
uniphy autoneg time out!
Does anyone have an idea how is that autoneg time managed or what could have changed that time in NSS builds rather than in recent regular OpenWrt builds that don't suffer the autoneg time out issue.
understood ... so, I am still using the old method of loading the firmware via the u-boot... i tried the patch that enabled the load via userspace and didn't worked this was sometime ago
I'm running @qosmio -skb built on the weekend with HEAD@9fd5ca5fce9f53cecd6709270323749d504ffd2c , ATH11K_MEM_PROFILE_1G, NSS_MEM_PROFILE_HIGH, pbuf auto, mosquitto-ssl, adblock-fast, and a few small conveniences on WRX36 (otherwise using @qosmio's .config).
Build seems to be a real winner. I'm getting consistent 925/925 on the wire, 1625/925 on wireless, memory used VERY stable in the range of 61.6 to 62.4 MB -- online since Sunday afternoon with no measurable leakage, IPv4/IPv6 connectivity all good.
Now what to do with all that extra/unused memory/CPU?
@adamhnat
Just half an hour running after a reboot.
Will continue to monitor it.
Edit (Important clarification ) - Seems that I've compiled this build before skb was pushed to the NSS wifi branch. So take all of the data here only as a reference and to compare the NSS build performanse right before the skb introduction.
@sppmaster@Trying2023 : can you note Slab mem usage across few days? In my case it's growing very slowly cat /proc/meminfo | grep -e ^S
and note down Slab, SReclaimable, SUnreclaimble
in my case after 36h:
Slab increased from 95MB into 103MB
SReclaimable 13MB to 13,5MB
SUnreclaimble 83MB to 90MB
Cache: 46MB to 48MB
I've compiled with 512MB profile on AX3600 and set skb to auto.
in my case memory looks like that (before noon is non-skb firmware)- it's growing slowly but constantly.
Note the top of the memory jumping around. The sudden drop was when I set pbuf auto. Since then it seems to be moving both up and down as needed, no problems indicated.
ax6 512m firmware compiled with qualcommax-6.1-nss-wifi-skb and qca11.4, memory usage! The proxy plug-in, frpc software, and smartdns software are run！
I have only one wifi 6 client that supports 160MHz and it is 2400/1900 mostly (like your third client).
I have two other wifi 6 clients that are 80MHz and they are 1200/1200.
And these are achievable because each of them can get 1Gbps during speed tests.
I think it's an excellent device.
Did you by any chance install procps-ng-ps? Or unselect CONFIG_BUSYBOX_DEFAULT_PS? LuCI process display only works with the busybox version.
I've merged in the changes from qualcommax-6.1-nss-wifi-skb into qualcommax-6.1-nss-wifi, so you should be good with building like before.
What was the original issue you had? It would crash on booting up? I know you were running the QSDK 6.1 backports, have you tested from my branch since then?
hi @qosmio so yes I have been testing with the dynalink and unfortunately suffering from high upload latency (it has to be something upstream so not much worried about it)... but the ax9000 was the first reason by christmas to go awol and hack using the qsdk backports. it was all fine with the hack just tried today straight out of your default repo and it crashed ... will share tomorrow the logs. thank you
I couldn't find CONFIG_BUSYBOX_DEFAULT_PS option in menuconfig - busybox customize, but I have this in my config file CONFIG_BUSYBOX_DEFAULT_PS=y procps-ng-ps is not selected.
