From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id EC6143B2A4 for ; Tue, 20 Aug 2019 13:47:18 -0400 (EDT) Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id EDAD789AC2 for ; Tue, 20 Aug 2019 17:47:17 +0000 (UTC) Received: by mail-ed1-f71.google.com with SMTP id n7so3855093edr.5 for ; Tue, 20 Aug 2019 10:47:17 -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:cc:subject:in-reply-to:references:date :message-id:mime-version:content-transfer-encoding; bh=l1ag/h1kQ8mbhE4SxQ0CPTmKesDb/dUgs5PXW7Ka8wk=; b=jtt0xOBSwbVKFeFOXkOl97K44NCtbsCuulWQ/gkaOnugUn33OGO93tYH7/ZDmONen1 LZqrXbnHAAyQXWQiWJG/vVhJNcngUb9sLdGYrry5lfqnhUQdet5CnQMBkNnwsGTCrT7B Kld6T7dq0TO9/DumWSBXZgod01mTpF3GCDPHOMPl/UbwdPdHila9hqDXUTZQFrOHXbpY TJRFjGgNaA+PmedYfU2QjG3Kis+gu3s/XJd8lX7TAaCgnBYe6nPYvzNBf6SNjM/LMAlR kTHYG6C0qBBTrqqxuQ94w8hF3TA5xQaTiHLuK+WJ2d4BBjMaxam02P1wtAXXohVF+KiP r16Q== X-Gm-Message-State: APjAAAVnVz2bdtA5ke17myQWVgVwDDyQkMynNHH5hWff6c1ttsP6Vk5V RCBw1byfNYWxYqm8jzHKXvrIk1evqcbcCEVeVuqndGNcSoRUtH/dlbdepGn7Ec2DUQyBV1rEAcE R53zc+eUgs0O4E6KAiRbM5Q== X-Received: by 2002:a05:6402:1285:: with SMTP id w5mr32868342edv.36.1566323236625; Tue, 20 Aug 2019 10:47:16 -0700 (PDT) X-Google-Smtp-Source: APXvYqw2BeIJG7RCH893/jtIFWvm0qp9biDkjd/2jRD16ZmmsYFxQWrJAeo1E+yHeyzBlGU5FeoMHA== X-Received: by 2002:a05:6402:1285:: with SMTP id w5mr32868279edv.36.1566323235922; Tue, 20 Aug 2019 10:47:15 -0700 (PDT) Received: from alrua-x1.borgediget.toke.dk ([2a00:7660:6da:443::2]) by smtp.gmail.com with ESMTPSA id g3sm2628215ejj.69.2019.08.20.10.47.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 20 Aug 2019 10:47:14 -0700 (PDT) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 34792181CE4; Tue, 20 Aug 2019 19:47:14 +0200 (CEST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: Sebastian Gottschall , Dave Taht Cc: "cake\@lists.bufferbloat.net \>\> Cake List" In-Reply-To: <6782ec15-30eb-63b0-f54f-376c5e6b840b@newmedia-net.de> References: <384866b4-4c91-cf2c-c267-ee4036e5fbf7@newmedia-net.de> <87wof7sriw.fsf@toke.dk> <6782ec15-30eb-63b0-f54f-376c5e6b840b@newmedia-net.de> X-Clacks-Overhead: GNU Terry Pratchett Date: Tue, 20 Aug 2019 19:47:14 +0200 Message-ID: <87tvabsp99.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Cake] cake in dd-wrt 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, 20 Aug 2019 17:47:19 -0000 Sebastian Gottschall writes: > Am 20.08.2019 um 18:58 schrieb Toke H=C3=B8iland-J=C3=B8rgensen: >> Sebastian Gottschall writes: >> >>> Am 20.08.2019 um 18:24 schrieb Dave Taht: >>>> On Tue, Aug 20, 2019 at 5:09 AM Sebastian Gottschall >>>> wrote: >>>>> :-) i'm following this list and yes we are working on bringing cake i= n :-) >>>> Yea! thx for being on the list! >>>> >>>>> is there any question behind this link from your side? >>>> I just wanted to make people here aware that it was happening. >>>> >>>> Is there a build now? >>> the first builds with cake are already out yes, but unfinished. we >>> started then to rewrite major parts of the qos code. i expect to push o= ut >>> a new build tomorrow. it will still not use the full potential of cake >>> since we have to bring all together with the priority and ndpi and >>> filter based filter together >>> with the cake scheduler. >> Are you aware that you can use the tc filtering functionality to make >> this play along with cake's tiers? > we are already using filters. yes. its just that cake is acting always=20 > as root and we have different sorts of qos configurations. so you have=20 > wan. but we may have multiple lan interfaces with individual qos=20 > settings. the same for mac / ip based user settings. so in fact we need=20 > to create a individual qdisc for each of these setting types in worst=20 > case, but in that case we cannot take in account the global available=20 > bandwidth anymore. Ah, right, I see. So this is things like users wanting to limit a specific type of traffic to a certain bandwidth? >>>> Are you using the out of tree version or mainline? Out of tree has >>>> some experimental SCE work >>>> that I'd love to see tested at more scale but not actually shipped at = this time. >>> out of tree straight from git with modifications to be compatible to my >>> kernels since your compatiblity layer is mmh not perfect. >> Please do feel free to send a pull request with your fixes for the >> compatibility stuff! :) > will do after i have taken out specific mods for my kernels again. Great, thanks! -Toke