Am 16.09.2019 um 16:06 schrieb Jonathan Morton:
If you're able to log in as root, what does "tc -s qdisc | fgrep memory" tell
you?
its not my device. i need to recreate his setup (of the reporter) on my
testbed first. then i can show you the output.
Cake actually does very little dynamic memory allocation. There's a small amount of
memory used per queue and per tin, which should total less than 100KB in
"besteffort" mode (which you should be using if you have manual traffic
classification).
bestefford is used. yes
All other memory consumption is due to packets in the queue, which are
allocated by the kernel when they are received, and deallocated when
transmitted or dropped. Cake applies a limit to the memory used by queued
packets, generally 4MB by default. The only way this can be exceeded by more
than one packet (transiently, when a packet is enqueued and Cake has to drop
other packets to make room) is if there's an unaccounted memory leak somewhere.
If you can find such a leak in Cake, we'll fix it. But I think it is probably
elsewhere.
even if elsewhere i'm wondering why only cake triggers it. there is
nothing different in between when comparing with other schedulers
i dont see a leak here. i more see a massive consumption here. i can run
cake on devices with more memory and it will not run out of memory.
the assumption is that cake takes the 4 mb memory per qdisc and i have
alot of qdiscs
- Jonathan Morton
_______________________________________________
Cake mailing list
Cake@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cake
