From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 971D4C3A5A6 for ; Tue, 27 Aug 2019 21:09:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6C7DA206BF for ; Tue, 27 Aug 2019 21:09:43 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="UITFoLLX" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729903AbfH0VJl (ORCPT ); Tue, 27 Aug 2019 17:09:41 -0400 Received: from mail-wm1-f46.google.com ([209.85.128.46]:34897 "EHLO mail-wm1-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726871AbfH0VJl (ORCPT ); Tue, 27 Aug 2019 17:09:41 -0400 Received: by mail-wm1-f46.google.com with SMTP id l2so546759wmg.0; Tue, 27 Aug 2019 14:09:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=+B2wB2GTqpND8w0IW6Qck36+/TjuYm3B66Fsdg7FXWo=; b=UITFoLLXJUA6vbdatFUMetI8NTy87NA2+0/5G9hOmz8Mfd0/L824VuipjDPpRiprmM aeuUAq8r1qdUAd6czv/XHW8gUD39BHff52XiDHibvvFVjJLoXqEogWXvhq/vBqX3lSAD u09x/NFELfpsAqM8btPi9+tYR65NXsZpehvtbzCMqNGYc8CZQfRiM/Dz9PovwPGDAKUR dUZ2EVQbfgDsiZ6Q6jN7HXugyk2AIrSn+CMiviwPpvvnLiC6Wt6k7AYwHzFAq8jWxevg K9QconDBgV5vBwApb5jBwgmFvWCNo9wsG/hVcbrWG+UYyYA6VFP5apsp1+hKpmxv2OYJ oUZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=+B2wB2GTqpND8w0IW6Qck36+/TjuYm3B66Fsdg7FXWo=; b=YEIG1RE1oSFxTgMIZVvQNbEZvXUhNeG1ZIaaeuLpY+NiKAsZ0kGCAEZMfaN5QtyIfI 9O/QWdkDZwTepn9tNEuPjxn+fHnfX0QA0J+sXxbEOXMSk+GcRWsM6+P68k/JRwJ/yIRq yR1R2pybRfi9T5YMA9fcj7xABKm/EpubQWVjJqAi5BvJxxhb8nQksRBZMsNYIBGjb61k 9PN7XurHLW1Svde/kzxdhRvBKg0zH0NethTa7OVMI1VkuOKS3Hr/qRbSnnvhPG+fBfOH 5v5Kr08IvftG74txkcCaT/RoDUTt7l5DicgQdAaZlhYF4No4yyhqNH2KiLCx2JY4CMVr MAHQ== X-Gm-Message-State: APjAAAWO2LG0n0wcoOb+p/9FLYZv+lSARTi/oRgR0XhQP7la+gbZBlg3 gAKkx0Dv5bNG5Xhf0OZ1kndoonX8 X-Google-Smtp-Source: APXvYqwOoTEvnBxrtV3Ggx0IgwKDLyXObcAl9kk1qfVAxKYBwW3uh65HUt+lRp3vuWWKOcgt0u+b4g== X-Received: by 2002:a1c:c706:: with SMTP id x6mr579525wmf.104.1566940179017; Tue, 27 Aug 2019 14:09:39 -0700 (PDT) Received: from [192.168.8.147] (212.160.185.81.rev.sfr.net. [81.185.160.212]) by smtp.gmail.com with ESMTPSA id a6sm254165wmj.15.2019.08.27.14.09.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 27 Aug 2019 14:09:38 -0700 (PDT) Subject: Re: Unable to create htb tc classes more than 64K To: Dave Taht , Eric Dumazet Cc: Cong Wang , Akshat Kakkar , Anton Danilov , NetFilter , lartc , netdev References: <9cbefe10-b172-ae2a-0ac7-d972468eb7a2@gmail.com> From: Eric Dumazet Message-ID: <48a3284b-e8ba-f169-6a2d-9611f8538f07@gmail.com> Date: Tue, 27 Aug 2019 23:09:36 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: netfilter-devel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netfilter-devel@vger.kernel.org On 8/27/19 10:53 PM, Dave Taht wrote: > > Although this is very cool, I think in this case the OP is being > a router, not server? This mechanism is generic. EDT has not been designed for servers only. One HTB class (with one associated qdisc per leaf) per rate limiter does not scale, and consumes a _lot_ more memory. We have abandoned HTB at Google for these reasons. Nice thing with EDT is that you can stack arbitrary number of rate limiters, and still keep a single queue (in FQ or another layer downstream)