Qualcomm Fast Path For LEDE

Community Builds, Projects & Packages
479

Short version:

I put back gwlim's original version of this patch (without removing anything, I also edited my 2 recent posts above) and using it with SQM@WAN:

  • it almost 2x faster then dissent's one and rock stable (I used it for a month before)
  • dissent's one disabled pastpath acceleration after around 5 mins on intesive SQM ingress use

Edit: it turned out gwlim's patch doesn't work with SQM ingress.

Longer version:

I streamlined building firmware so everything is the same (including config files as well) apart from the SFE kernel modules between the 2.
Both firmwares are built on lede-17.01@a006b48 (2017-08-29) branch and contains gwlim's amazing patchset.

  • gwlim patches
  • dissent1's patch for lede-17.01 branch (instruction is included)
    -- note: I also went through all the applied kernel patches whether they are fine

Test setup:

  • Archer C5 v1.2 (mips74k, 720MHz, 128RAM, 16MB)
  • net: PPPoE, 76Mbits/20Mbits, ipv4
  • SQM@pppoe-wan, cake/layer-cake, 87500/24500, ATM:44
  • a laptop without VPN connection
    -- run a torrent client with 1 (same) download at max speed
  • another laptop with VPN connection
    -- stream music in the meantime
  • run htop (in tmux) on router to see CPU % (or top for sirq)
    -- that's the best indicator whether SFE and SQM works well indeed

Results:

dissent1's version:

  • until 5 mins: down 8900 KB/s , up 1600 KB/s , number of connections ~70, htop ~56%
  • after 5 mins and another 10 mins (till the end of test): htop ~80% !!!
    -- that means something broke!

gwlims's version:

  • down 9000 KB/s , up 1300 KB/s , number of connections ~70, -> htop ~30%

So, I suggest to look at sirq usage if you use dissent1's version with SQM.

1 Like