From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::22e]) (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 BFB173B2A4 for ; Fri, 7 Apr 2017 04:13:34 -0400 (EDT) Received: by mail-wr0-x22e.google.com with SMTP id o21so67721087wrb.2 for ; Fri, 07 Apr 2017 01:13:34 -0700 (PDT) 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=nnFOAIOvRIW9iOFR2GaRNeZz8toPvD5/8ibeHgQfdo4=; b=axk6WGwRmEENQVesHRttOcUgNPYW5VgTx/DVuos3YnnPIQNAqDqGCtK7EDJ0/DHAky UhxUGPxE71Xhl1WD7cMDfzPVc73CKL9xWw6nMJ16qevfeaX2urXVgQi8+T6GM/DPrlxy wLrbMw+XZVaskahTpNHMobsRl0iq5QTD2lsM8JEhIov+xAncsHw8zy2Xh2DNuTVBeoZT Ym8Fq1JCNPceTKt7uhnR2IbG65iOEoj1csTNyKDCMC2PB1CIcshkGJfIyq0+nQpgtdaC CNMx5sGYRPQn2ExI8Qu73jLYD/d293AcLs5JSgDLvfA6PbSq+2ldPncJfDpMUKNxUXhb Y1mA== 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=nnFOAIOvRIW9iOFR2GaRNeZz8toPvD5/8ibeHgQfdo4=; b=WG24cjKdXEH6G94kGk1AM7S5FF+TLiMCgkxWXbz5jdVCTmOPAYKdA/Gtbac6vYnG8Z ZeEiIRcdq8MyxxgB5NCstwkvlgltVEbzEAzoYUJSZ3em2X8UIDl6Z1GBhzfwziWWa5Qj Ey9oMcDZahDqyqcxqI5ob53xohv/dIzA0y8xwvVpwY5B8nCaBoLxz092d4TOLhI8Es86 ugAQ5ldTSX64sUKwg4GBtVNnWoy1p/53e7l2EKLUMIVEZNyxXVQ4l3QTtlBORfFFDZed Jjb4Uo/Sp5mPj0YmY07L/ijj55K7S6e4qBWFWL7yMVCdnE5p4n4X7sDV+cAK+uUjfP1n DFNA== X-Gm-Message-State: AFeK/H0YE6Drciq6A2weGMZB5TI0osjWZDouEJAWbNC3nWm87uLsIj0kYuni7px6Aw811A== X-Received: by 10.28.46.213 with SMTP id u204mr26835951wmu.136.1491552813872; Fri, 07 Apr 2017 01:13:33 -0700 (PDT) Received: from [10.72.0.130] (h-1169.lbcfree.net. [185.99.119.68]) by smtp.gmail.com with ESMTPSA id h68sm2764469wmd.19.2017.04.07.01.13.32 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 07 Apr 2017 01:13:33 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Pete Heist In-Reply-To: <1E4563E2-63E2-419D-AFDD-8CD74F22539B@gmail.com> Date: Fri, 7 Apr 2017 10:13:31 +0200 Cc: cake@lists.bufferbloat.net, =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= , =?utf-8?Q?Dave_T=C3=A4ht?= Content-Transfer-Encoding: quoted-printable Message-Id: References: <2FD59D30-3102-4A3E-A38E-050E438DABF0@gmail.com> <6F118C46-16DB-48AC-A90D-7E6D44B6D069@gmail.com> <1E4563E2-63E2-419D-AFDD-8CD74F22539B@gmail.com> To: Jonathan Morton X-Mailer: Apple Mail (2.3124) Subject: Re: [Cake] flow isolation for ISPs 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, 07 Apr 2017 08:13:35 -0000 > On Apr 6, 2017, at 11:26 AM, Pete Heist wrote: >=20 >> On Apr 6, 2017, at 11:11 AM, Jonathan Morton = wrote: >>=20 >> On 6 Apr, 2017, at 11:27, Pete Heist wrote: >>>=20 >>> There is a table of member ID to a list of MAC addresses for the = member, so if there could somehow be fairness based on that table and by = MAC address, that could solve it, but I don=E2=80=99t see how it could = be implemented. >>=20 >> One option would be to use HTB with FLOWER filters to sort out the = subscribers into classes, and use Cake or fq_codel as a child qdisc per = class. Remember that Cake can be used in =E2=80=9Cunlimited=E2=80=9D = mode to rely on an external shaping source. One more thought, would it be possible for Cake to optionally include = the packet=E2=80=99s mark in the hash? I know it=E2=80=99s additional functionality, and another keyword, but = it could get you out of the business of the myriad of ways people might = want to do flow isolation, and you=E2=80=99d still have a catch-all = answer for such cases. There could be a keyword =E2=80=98hash-mark=E2=80=99, let=E2=80=99s say, = which first includes the mark in the hash, then does on to deal with any = other flow isolation keywords as usual. So for example if I have = =E2=80=98hash-mark=E2=80=99 and =E2=80=98dual-srchost=E2=80=99, the hash = is first on the mark, then by source host, then by flow. I could set the = mark to be the member number with iptables. It looks like the mark could be obtained from the =E2=80=98mark' field = of the sk_buff struct, but I don=E2=80=99t know the validity of the = field in various cases. For example, I don=E2=80=99t think I can set the = mark on ingress before it reaches a qdisc on an IFB device.=