From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from webmail.newmedia-net.de (smtps.newmedia-net.de [IPv6:2a05:a1c0:0:de::167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id B489F3CB36 for ; Tue, 17 Sep 2019 01:12:25 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=newmedia-net.de; s=mikd; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject; bh=Jakg/0cZHjQ7dKuurogneH9Cf5Im3/xNzlKgVEBKPn0=; b=jKxkWemB838Ak1d8/o/V52WYykqzoP0V8+f1PVMn9VinbMMyHSRFE1XJogze/FVkXZu2ETX14Bh//F9RZNamf8YWg1Rbi/KXKvu45WATlcuB0fguvvjdv7Csf/zUJ5SoM+OtJhVw6FOm3zqgUbPCf8oUeFFzOQPFwE+DsI6FBNc=; To: Jonathan Morton Cc: cake@lists.bufferbloat.net References: <2825CE14-2109-4580-A086-9701F4D3ADF0@gmail.com> <18b1c174-b88d-4664-9aa8-9c42925fc14c@www.fastmail.com> <9a90111b-2389-4dc6-8409-18c40f895540@www.fastmail.com> <43F02160-E691-4393-A0C0-8AB4AD962700@gmail.com> <057ea708-6797-23f5-ef01-9d3d7b002578@newmedia-net.de> <93040b26-aa44-41b9-abec-7e1f637c0cb1@www.fastmail.com> <2FE4FDA8-BB22-4216-8D97-FA05D896E54B@gmail.com> <99196e48-926e-689d-b1a8-69b1bfb1885f@newmedia-net.de> From: Sebastian Gottschall Message-ID: <3de7bfb5-3393-f10e-1ffa-be46b798cea4@newmedia-net.de> Date: Tue, 17 Sep 2019 07:10:54 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Received: from [2003:c9:3f21:2600:e48d:ccf8:4911:ed41] by webmail.newmedia-net.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from ) id 1iA5mz-0007eV-0v; Tue, 17 Sep 2019 07:12:33 +0200 Subject: Re: [Cake] cake memory consumption X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Sep 2019 05:12:25 -0000 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