From 2792285667e1dbc79c4e982c289322fc183ec66d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Chac=C3=B3n?= Date: Tue, 13 Jul 2021 11:50:41 -0600 Subject: [PATCH] Update README.md --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 03b87700..0e4bbc2a 100644 --- a/README.md +++ b/README.md @@ -81,6 +81,8 @@ Bloat is below 5ms in each direction. * Shape Clients by Access Point / Node capacity * APs equally distributed among CPUs / NIC queues to greatly increase throughput * Simple client management via csv file +## Considerations +* Each Node / Access Point is tied to a queue and CPU core. Access Points are evenly distributed across CPUs. Since each CPU can usually only accomodate up to 4Gbps, ensure any single Node / Access Point will not require more than 4Gbps throughput. ## Limitations * Not dual stack, clients can only be shaped by IPv4 address for now in v0.9. Once IPv6 support is added to XDP-CPUMAP-TC 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).