From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 65ECA3CB44 for ; Thu, 8 Mar 2018 16:46:55 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1520545614; bh=ZpJNnIY9+cHQ8yFZlIjtWVdr23KvgQRoavVIHb9ZIRQ=; h=From:To:Subject:In-Reply-To:References:Date:From; b=VZK/84iIr2f8mfeKIZtA41E4kyPhzT8Bv1k8k07mKUvFwZupBHpyQ+AzNjyNn4bbR RDn5snOO/eAmAGRPckN9N9bw21wDADK6gdW9htmgHNLV593bIYzxfrFwVwKDvCCs6h 2G/LpDj5EBNu9I5oCIAMQVKOA/qauh2ZMuXMXegfSOI714PKNxT0Onp3193jJhmyno y93GXwnilQCMDRruWRGXbJwgsjBVgmzDrD9FmVts0abc/0S6WnlqVN/hIxXRPjoLvf osUIThT9Xb/zDbmHHbeldj1L0w/hZw9BVkxGNkFoO/6zp3hrda/HFg1wu7F5hcfLTr GWATQrmgeL+vQ== To: Dave Taht , Cake List In-Reply-To: References: Date: Thu, 08 Mar 2018 22:46:53 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87371akzoy.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Cake] >40Gbit shaping 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: Thu, 08 Mar 2018 21:46:55 -0000 Dave Taht writes: > While it seems unlikely we'll get to shaping past 40Gbit any time > soon, perhaps changing the API to 64 bits to specify bandwidth will > avoid problems in 2024, or with (one day) offloaded hardware. Might as well. There is not really much of a performance reason to keep this at 32bit, is there? -Toke