From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-1.mimecast.com (us-smtp-2.mimecast.com [207.211.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 4E5403B29E for ; Wed, 18 Sep 2019 05:54:04 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1568800444; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=pnYpSjrtMPgn+5Q3vrHhxTHkPwXC69f2EB98iGGeCrw=; b=QH83cyePwZcmSn/ydIuqjrZBU+FtCAf0U+mZh2Lrepf4g5a9hvrZvS4BuRrKVQO3NLkfZ+ lviVR332azcFulaTleTOsdfZLNCNOYfQt3CnpeyRIsTrx+CnYQ90K2t9nASF56p3DYksK0 cjkuZjzPrMzZ3vniXWvTd9N/76LwJDI= Received: from mail-ed1-f72.google.com (mail-ed1-f72.google.com [209.85.208.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-361-gzO5BE6iMrO4YDIEpUB4fg-1; Wed, 18 Sep 2019 05:54:01 -0400 Received: by mail-ed1-f72.google.com with SMTP id h12so1372167eda.19 for ; Wed, 18 Sep 2019 02:54:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:references:date :message-id:mime-version; bh=L7b93gUDX3VjwMrd4eYQ5bCWVj3OrB1HdfXxGtwmcro=; b=UJE6xjV1UVp4uqA5wfzmA247dqWBwj/oolbgv0XlYse9FqfOkIfavSz67DPqkgysbZ sGLS6tpSjnY/lj0ZQcOEJyLCriOXQd9/4s8b7Bcj1wL/+vHAMd8XWdb8mq+qr0/NDQo8 mKcpprj1DrEhg1idk7g+k4pXNg2kogiiBPBb/w6E9IkPL9+JfXETe+m0a/RR+qgbzwXg bJSUl4nE3SZNuo1aFLE2o524ESuECJJJILyRku6QC37/XmxsyaMgiONh9to3TNBokuUr 4GF8IYonIBsqHau6MQIHfEzXUEhz/2XHjON8CIEO7DgpbqLVwxWZ0fONjOQ76rXvdVYI zJOA== X-Gm-Message-State: APjAAAW4JI4xwk7q8aMoM/zf/pKhdqKux95pg7q3MvjWvBmFpOfGDe59 qdXXZDl1hnbFAzYvWMkzV969HJmeXVWQUOu3QGHYNQzoMtcG3beM/LGunA8KVHVBbl5UTbDdKmm UU2eUjjEoeaWscjs0OGx/WQ== X-Received: by 2002:a50:c908:: with SMTP id o8mr9312959edh.187.1568800440070; Wed, 18 Sep 2019 02:54:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqyDOOuf/axGNMy2Y0poZp8s70QUPVEKdYFp9rkOfBTtlE2UWrkahu+6xZXCzSGHyqRdn/JEUw== X-Received: by 2002:a50:c908:: with SMTP id o8mr9312951edh.187.1568800439933; Wed, 18 Sep 2019 02:53:59 -0700 (PDT) Received: from alrua-x1.borgediget.toke.dk ([2a00:7660:6da:443::2]) by smtp.gmail.com with ESMTPSA id l12sm940319edw.29.2019.09.18.02.53.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 18 Sep 2019 02:53:59 -0700 (PDT) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 8494418063E; Wed, 18 Sep 2019 11:53:58 +0200 (CEST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: Sebastian Gottschall , cake@lists.bufferbloat.net In-Reply-To: <3449acf8-e700-6b50-544f-b272165ad0e6@newmedia-net.de> 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> <878sqomoj4.fsf@toke.dk> <87h85cl4qk.fsf@toke.dk> <87r24fjm60.fsf@toke.dk> <3449acf8-e700-6b50-544f-b272165ad0e6@newmedia-net.de> X-Clacks-Overhead: GNU Terry Pratchett Date: Wed, 18 Sep 2019 11:53:58 +0200 Message-ID: <877e66hqvd.fsf@toke.dk> MIME-Version: 1.0 X-MC-Unique: gzO5BE6iMrO4YDIEpUB4fg-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable 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: Wed, 18 Sep 2019 09:54:04 -0000 Sebastian Gottschall writes: > the problem is. i tested restricting the memory to 4 mb. but it still=20 > runs oom. same memory consumption and from the qdisc show output i also= =20 > see that just a few kilobytes are used in that pool. > so the problem with cake must be somewhere else. its not the buffer=20 > limit. i see values like memory used: 22176b of 4Mb which is really=20 > nothing. most qdiscs are 0 and unused in that setup Hmm, that does sound odd. Are you seeing the "total used memory" go up as soon as you load the qdiscs (without any traffic)? Does the memory drop down again if you clear the qdisc config and go back to an fq_codel-based one? -Toke