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 C13373BA8E for ; Sat, 5 Jan 2019 06:17:23 -0500 (EST) Date: Sat, 05 Jan 2019 12:17:13 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1546687042; bh=9vlVtWHFn50dsj1bWyhMU7dnbJqaimzTM+4vxG3CXKI=; h=Date:In-Reply-To:References:Subject:To:CC:From:From; b=mvYwzyDnoNBCJbLnMgNdqXqiZ93aY6NCs+N1bqpFksIlLD+PCTrBN8NV0b1mnf2SG 3KKWd+x3z7/QxkMd6HWZ3+FJBmeYW1YPfoSWr1YoPbG4yYdYIUVfdIOC2vpcdhgV+p DbfsUiVzugp9Fz0KV/vqGpfvd6+0gshDBWwG6HRaunsdoAfWwaZ0yIVaqdMxaXW7sv Jkk1NvgbiPyv5MQdu7omJVa3u6uOz347F5W6BLZCgKvGeucBksBJMNjfT8h27cRWTW jtB5JieC0QeXWCju3iqyg5b23fTeYLsetHVPUK/5O4Qgw+J84H3LSsMB60bLxmo0NN aI8iTNWE2+XtA== In-Reply-To: <192239C1-A1F1-4A25-B190-273A1DA210F9@gmail.com> References: <5482A3CA-9C36-4DDE-A858-24D8467F70C7@heistp.net> <8736q8yumt.fsf@toke.dk> <4C422792-7E51-4DBA-A229-FA7D3F987FB6@heistp.net> <87zhsgxdao.fsf@toke.dk> <192239C1-A1F1-4A25-B190-273A1DA210F9@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable To: Jonathan Morton CC: Pete Heist ,Cake List From: =?ISO-8859-1?Q?Toke_H=F8iland-J=F8rgensen?= X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <9D64E984-F9E8-4FF5-9114-5DE359780558@toke.dk> Subject: Re: [Cake] cake infinite loop(?) with hfsc on one-armed router 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, 05 Jan 2019 11:17:23 -0000 On 5 January 2019 11:44:44 CET, Jonathan Morton = wrote: >> On 5 Jan, 2019, at 12:34 am, Toke H=C3=B8iland-J=C3=B8rgensen >wrote: >>=20 >> This basically means that we can't use CAKE as a leaf qdisc with GSO >> splitting as it stands currently=2E I *think* the solution is for CAKE >to >> notify its parents; could you try the patch below and see if it >helps? > >Is this also a problem on current kernels, or only older ones? Newer ones as well (I assume - haven't tested)=2E -Toke