IntenseWebs/LibreQoS
3
0
Fork 0
mirror of https://github.com/LibreQoE/LibreQoS.git synced 2024-11-26 02:00:15 -06:00
Code Issues Packages Projects Releases Wiki Activity
939f7af7a0
LibreQoS/v1.0
History
Robert Chacón 30015d4267
Update README.md
2022-09-11 13:25:34 -06:00
..
Integrations Updated v1.0 2021-12-05 12:11:49 -07:00
xdp-cpumap-tc@888cc7712f Added xdp-cpumap-tc submodule 2021-12-05 12:12:57 -07:00
AccessPoints.csv Updated v1.0 2021-12-05 12:11:49 -07:00
ispConfig.py Update ispConfig.py 2021-12-11 11:24:57 -07:00
LibreQoS.py Update LibreQoS.py 2022-05-15 18:12:03 -06:00
README.md Update README.md 2022-09-11 13:25:34 -06:00
scheduled.py Updated v1.0 2021-12-05 12:11:49 -07:00
Shaper.csv Updated v1.0 2021-12-05 12:11:49 -07:00
Sites.csv Updated v1.0 2021-12-05 12:11:49 -07:00

README.md

v1.0 (IPv4) (Stable)

Released: 11 Dec 2021

Installation Guide

Features

Can now shape by Site, in addition to by AP and by Client

Considerations

If you shape by Site, each site is tied to a queue and CPU core. Sites are evenly distributed across CPUs. Since each CPU can usually only accommodate up to 4Gbps, ensure any single Site will not require more than 4Gbps throughput.

If you shape by Acess Point, each Access Point is tied to a queue and CPU core. Access Points are evenly distributed across CPUs. Since each CPU can usually only accommodate up to 4Gbps, ensure any single Access Point will not require more than 4Gbps throughput.

Limitations

As with 0.9, not yet dual stack, clients can only be shaped by IPv4 address until IPv6 support is added to XDP-CPUMAP-TC. Once that happens we can then shape IPv6 as well.

XDP's cpumap-redirect achieves higher throughput on a server with direct access to the NIC (XDP offloading possible) vs as a VM with bridges (generic XDP).