From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [45.145.95.4]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id C51983B29D for ; Sat, 26 Feb 2022 15:10:07 -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=1645906206; bh=eVpf4IEB9GQ0yGz6BSng79Ddxfrq0U8jgPuLux4eEN8=; h=From:To:Subject:In-Reply-To:References:Date:From; b=kKlo7QJOyWjcAvj8Bgl1w/ljVrnNIPDS1/Ykd/NPmE+huNNfm1k/M7RFaysQ49Yz/ GxCmka4vnBCN/ghYe5p9ZrwHAUW+uUQ+PprD8XkAGidY+DTXCtk2XvXKkK+fKt/2Rh c5vt8Yynu1Fu9SD+BJCsZ6MrMTNFrCGJZVvPn1IQyx4AXqSr0iTvtQI2wcK3RtPfnl jEwz9a7eQfxKpiLMfr/bhPTfoQRoXhGLFdikMFNoapy1/WbmfvhJ3aEedK0lSGrLic 65st8FfDhOWH7U1FAXJg+fFQdbsnDal9dBfOsLh1dYNAZ8t3Nwqg6Kfc/6o3/rtv+7 l/lHq3KhFPS9g== To: Jim Geo , cake@lists.bufferbloat.net In-Reply-To: References: Date: Sat, 26 Feb 2022 21:10:06 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87ilt1v17l.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Cake] cake ingress switch 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: Sat, 26 Feb 2022 20:10:07 -0000 Jim Geo writes: > Hello, > > Was it the function of ingress argument in cake? > Checking online man pages, I couldn't find an explanation. > Does it make sense to use it on an ifb device? (sending ingress > traffic through it) Yes, that's exactly what it's meant for. The option changes cake's accounting so that packets that are dropped are accounted as part of the effective bandwidth of the link (since on ingress, even if they're dropped they have already traversed the bottleneck link). This should help keep the bottleneck under tighter control... -Toke