From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 0FB853B2A4 for ; Thu, 3 Jan 2019 00:18:25 -0500 (EST) Received: by mail-lj1-x22d.google.com with SMTP id t18-v6so28755786ljd.4 for ; Wed, 02 Jan 2019 21:18:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YavUjOAVzSZoTZYvHaomzrf/mMUfx36ylowTDrSB07A=; b=uQgyYP5xr/ezE0ME1s4vRJJylD9GBp82DC6lN4up69swIvZZRyZG39NFX8MLOJsp+8 AyLdZv84TDKX6LTw2wtlP6/ku1mAgEVcwwkZUIBoSF+Bi49Mflrh/TnwuTRNP79Ygg+y iepn3TA3G5ojtbIGsijblSGuu1kAGmpY3Uw1xMFyliYVWhZ8lWarDgJ2rFtXl+T5AwtN UzRo9zM1e+EmRy3lAX37S9HrJR7vCu6FN2z82rjpojmJz/aUF2Vs4YgDSpQS5VYgwIzD tLGtiBbzANzWR02VhXIk1p6atucmskLsI11ywfnFyyOzyuUUak0AwxJrclJhow5TXgpR YVsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YavUjOAVzSZoTZYvHaomzrf/mMUfx36ylowTDrSB07A=; b=Z4EcoQ+w7pJq9TxHJikrikJyZijnlFd259EyDGNEx2ZV5yN3NCeuLfKARmr97gCWss eI+uT2RGC7cAsR+lVVta4uJhuuw8ITK9JCnVXsr+FFWidWjNQ0GI4uXmby0vV8/N4DqY 6TOq4AyZHhV0PdPX83+nePs+p+AXLAAx3o7N8ywYbXJ5j6lGZgWhI/wLNa7SBnCcE7Ms QwgX6Kd88kJ0TZQoYos3yCQ/OirSOojrLGPNk4pwkiqm2WlcbXKj2SjV5K6ARM66/6UL CgKCuAS31ungJLsU1zm7XHZCEirqe9BDPdI/4GV+Ts7lj9VQ7tSSg/cqgrpaAG4yu0G8 KHPA== X-Gm-Message-State: AA+aEWYShDZ7331CwM7K31T9O0xQI8+MCzhmS4r/jf0JjlDHYYqga914 xEO7iPiSrab1s/tTDkXHprg= X-Google-Smtp-Source: ALg8bN7ysXVzTXL8S/s9riU15QPmYpu7eG2qTmf1jh5dzeJAOqa2deA84F2ni3VupTsa5iqREOYPYQ== X-Received: by 2002:a2e:b1ca:: with SMTP id e10-v6mr29109991lja.16.1546492703734; Wed, 02 Jan 2019 21:18:23 -0800 (PST) Received: from jonathartonsmbp.lan (83-245-238-230-nat-p.elisa-mobile.fi. [83.245.238.230]) by smtp.gmail.com with ESMTPSA id e14-v6sm11383983ljb.31.2019.01.02.21.18.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 02 Jan 2019 21:18:22 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Jonathan Morton In-Reply-To: Date: Thu, 3 Jan 2019 07:18:21 +0200 Cc: Pete Heist , Cake List Content-Transfer-Encoding: quoted-printable Message-Id: <3650A136-97A6-43F5-ADD3-B94A19775379@gmail.com> References: <8F9DE6A8-8614-46A8-9E9B-7B7E4CC7414F@heistp.net> <43a8ddec5beb962c53fe828363ecc839832de2c0.camel@gmail.com> To: Georgios Amanakis X-Mailer: Apple Mail (2.3445.9.1) Subject: Re: [Cake] dual-src/dsthost unfairness, only with bi-directional traffic 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, 03 Jan 2019 05:18:25 -0000 > On 3 Jan, 2019, at 6:15 am, Georgios Amanakis = wrote: >=20 > It seems if both clients are having bidirectional traffic, dual- > {dst,src}host has the same effect as triple-isolate (on both lan and > wan interfaces) on their bandwidth. > This shouldn't happen though, or am I wrong? If both clients are communicating with the same single server IP, then = there *should* be a difference between triple-isolate and the dual = modes. In that case triple-isolate would behave like plain flow = isolation, because it takes the maximum flow-load of the src and dst = hosts to determine which dual mode it should behave most like. Conversely, if the clients are communicating with a different server IP = for each flow, or are each sending all their flows to one server IP = that's unique to them, then triple-isolate should behave the same as the = appropriate dual modes. This is the use-case that triple-isolate = assumes in its design. It's also possible for triple-isolation to behave differently from = either of the dual modes, if there's a sufficiently complex pattern of = traffic flows. I think those cases would be relatively unusual in = practice, but they certainly can occur. I'm left wondering whether the sense of src and dst has got accidentally = reversed at some point, or if the dual modes are being misinterpreted as = triple-isolate. To figure that out, I'd need to look carefully at = several related parts of the code. Can anyone reproduce it from the = latest kernels' upstream code, or is it only in the module? And = precisely which version of iproute2 is everyone using? - Jonathan Morton