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 E2A233B29E for ; Fri, 1 Jun 2018 13:53:58 -0400 (EDT) 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=1527875637; bh=PP3hQzfi9Gv0zbCaLZ+Pe+tPqE/zgBwwkhN+l09yCpM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=NQDUnB1VT3LUnpY2kZGnCmzbcdp/eEfIJDDtMp3Rtl/81VxykDOLsOZI4P20SnguO zLS1HTsY3cajppYR9zsRynyPgHh+yVFg+2kh8iRCVMYwuFwoxbjscyHX4bWBJebeBc /hExS9+zWHZXX6Zk50g3KD1f9UIr+brzu8FAtlh46WMAnERSa7rt5peIaJAeNMfZfz /9qjjZWs+tgzJPOxzFGtCG27cKqgw3K3yk7BPvxwYu9ZeGf04l0H+v4g1g9lrI0WlI 6/xaFX6nVbgtaZxAkhwVvKAMbwxiHYQocmYwpXafMdsn9Ri4zocMTveb1GQnQ3Q3N/ 9dvp3ZXw4ecfg== To: Jonathan Morton Cc: cake@lists.bufferbloat.net In-Reply-To: References: <87muwe9z7j.fsf@toke.dk> Date: Fri, 01 Jun 2018 19:53:57 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87k1ri9yve.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Cake] Lockup at high speeds 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: Fri, 01 Jun 2018 17:53:59 -0000 Jonathan Morton writes: >> On 1 Jun, 2018, at 8:46 pm, Toke H=C3=B8iland-J=C3=B8rgensen wrote: >>=20 >> As you may have seen, I hit a lockup bug when testing Cake at high >> speeds. I am not quite sure what is happening, but we seem to be looping >> forever either in cake_dequeue() or cake_enqueue(), causing deadlocks. >>=20 >> Unfortunately, I have no more time to debug this for now. As far as I >> can tell, it only seems to be happening as the shaped rate approaches or >> exceeds the link speed, or when running in unlimited mode. So for all I >> know it might be possible to trigger it at lower speeds as well... >>=20 >> Anyone with any bright ideas? > > Is there a complete copy of the code somewhere I can look at it? I'm > still running the cobalt branch. I've been trying to keep everything in sync. The upstream-4.18 branch is identical to what I've been submitting; the only thing missing from the cobalt branch should be the classification stuff. The tests I just did where I saw the lockup was the current cobalt branch. -Toke