Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


View this topic in a long page with up to 500 replies per page Create new topic
1 | 2 
alavaliant
251 posts

Ultimate Geek
+1 received by user: 119

Subscriber

  #2820791 29-Nov-2021 06:51
Send private message

After several hours of testing I think I was seeing the occasional ipv6 packet loss described in https://bugs.openwrt.org/index.php?do=details&task_id=3373 so I turned flow offloading back off. I don't think I really need the extra speed right now and I'd rather have ipv6 working reliably. Will wait for further bug fixes / releases from the openwrt developers.



radiusq

9 posts

Wannabe Geek
+1 received by user: 2


  #2821149 29-Nov-2021 16:57
Send private message

Interesting - and you're on PPPoE delivered service right? - 

 

I'm curious to what this output looks like on your APU2..... - 

 

root@OpenWrt:~# cat /proc/interrupts | grep rx

 

  37:          0          0  654609083     968920   PCI-MSI 524289-edge      eth0-rx-0

 

  43:        255  311929213          0          0   PCI-MSI 1048577-edge      eth1-rx-0

 

  44:  328737080        383          0          0   PCI-MSI 1048578-edge      eth1-rx-1

 

  49:          0          7    2029570          0   PCI-MSI 1572865-edge      eth2-rx-0

 

  50:    2029570          0          7          0   PCI-MSI 1572866-edge      eth2-rx-1

 

Note - my PPPoE interface is eth0, and I've since limited the hardware queues on eth0 to 1. Prior to this change (which had zero affect on performance), I'd see something like - 

 

  37:          0          0  654609083     968920   PCI-MSI 524289-edge      eth0-rx-0

 

  *38:          0          0  0 0 PCI-MSI 524289-edge      eth0-rx-1

 

..note *38 is fudged as an example, but basically zero traffic would hit the second hardware queue.

 

Ideally you want each receive queue  bound to a different CPU to make use of a multi-core CPU....

 

I believe the RSS hashing algorithm was always placing PPPoE traffic in the same hardware queue - irq bound to the same CPU. Which means that PPPoE based traffic can not make use of multi-core CPUs.... would be good to see the output from your APU2 to confirm if you're getting 850Mb down in a similar scenerio....

 

This might interest you - https://blog.packagecloud.io/eng/2016/06/22/monitoring-tuning-linux-networking-stack-receiving-data/#hardware-interrupt-requests

 

 


1 | 2 
View this topic in a long page with up to 500 replies per page Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.