From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) by lists.bufferbloat.net (Postfix) with ESMTPS id A9ED33EDB9 for ; Mon, 21 Dec 2015 23:42:31 -0500 (EST) Received: by mail-lf0-x22e.google.com with SMTP id z124so117411060lfa.3 for ; Mon, 21 Dec 2015 20:42:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Y6SwtEJj73KYruekWzZoc8vy9caHk3WnphKsqQ5wnVo=; b=guPUBO1ySqD4DCN+yHnOdJ+B9A9wjlIRloy2NC5vAlYUuthFhgfbQJX6dJBvK0gDm8 V1hkyI3lQWwTUkwiYVYRiEkdRcX/HIhYUARZLZ4EJtAapeYGwRwYIbHMx9zjPLIYlCYl LLLaOapJvuIfHJ+QCI12pVG4D/IWcfIm2d7nryRZXpuiLgIYYI3JFd/tmDuM7Wi/N5CD c6Of6FkbyxCS16imzRcWZakuottM3irvftFoC7RU5hMV0l2E6ZAcMAmxRK1+by3ZRgbc RqhjR0Bt/NAKI74rpceLhN1cY1ecD7WvtYKWP1RoB+xl6VKiUbJ/pSH6VoNH2ZWXsTfA aWWA== X-Received: by 10.25.141.9 with SMTP id p9mr7828288lfd.112.1450759349966; Mon, 21 Dec 2015 20:42:29 -0800 (PST) Received: from bass.home.chromatix.fi (37-33-99-74.bb.dnainternet.fi. [37.33.99.74]) by smtp.gmail.com with ESMTPSA id kz5sm4166504lbc.7.2015.12.21.20.42.28 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 21 Dec 2015 20:42:29 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) From: Jonathan Morton In-Reply-To: Date: Tue, 22 Dec 2015 06:42:24 +0200 Cc: =?utf-8?Q?Bj=C3=B6rn_Gr=C3=B6nvall?= , cake@lists.bufferbloat.net Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Dave Taht X-Mailer: Apple Mail (2.3112) Subject: Re: [Cake] and the bad cpu news on arm is 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: Tue, 22 Dec 2015 04:42:32 -0000 > On 20 Dec, 2015, at 14:59, Dave Taht wrote: >=20 > I do happen to like the set associativity idea, but it's proving > really hard to show its value with any existing tests we have. Actually, your little experiment with dual-isolation inadvertently = showed how robust the set-associative hash is. Despite being = effectively reduced to an 8-queue system (between a single pair of = hosts), it was still able to keep four TCP ack flows, four UDP probe = flows and a ping flow effectively separate from four TCP bulk flows, to = the point where you couldn=E2=80=99t distinguish it from a properly = functioning version of Cake under the same load. Try *that* with a = plain, collision-prone hash function. - Jonathan Morton