From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-x22c.google.com (mail-pg0-x22c.google.com [IPv6:2607:f8b0:400e:c05::22c]) (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 D061D3BA8E for ; Mon, 11 Jun 2018 15:54:33 -0400 (EDT) Received: by mail-pg0-x22c.google.com with SMTP id d2-v6so10257686pga.13 for ; Mon, 11 Jun 2018 12:54:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=BdrB1QvFVvU2C4xlRgBUuGzc9XFVymD3/0OPl5tK6Uk=; b=npAL2DKkclPAugQdCq/ZcxN3YXs3PzZkI2c0xKbC1zSYefhqz/eOsm+mPLpu8gaHX1 Zeg8NYBv5FweF9uAHjKlR/KURteSPiv5w1t/bhRog5Avq4e5jJ5A2A7jOaf+Wb4GEPUD 6XJO9fHsn37UviTp5j/DnEncnDcpCfGmysBksbEIQNsECLu7qGLodrwI4RSF4ICCZpcz aZbPKcEMsrxLruMS5m/9a9JXeOTpgRBDDMETfQrpLVO0ijfb1SteksYcGwxE51wQkxOy 9WddihexN4sWYFzq3JaDN52gQvF1ctrFnHm0sjjcWt++xtqLYWH4bSb6svMVGLF1DALa qQzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=BdrB1QvFVvU2C4xlRgBUuGzc9XFVymD3/0OPl5tK6Uk=; b=LVNBkaMtzwiWzVjmgZ1n1mJduSmWryEBUuRHaH9XTaDoXocQ6ph9D0gsbHccDNyUgn aCqQap2QUmOrAj/GPK8gtHpyDFu1t7VXnTdxRlKQq1ZU2mSCxTjw+CqzHqZRoxko7nf1 nK4hhOLhpiezQMA8oYkcr17lYJA6pc+ygMtOGnXKA6JiY7fMoe/q9ACdu8Vyh2xC6ZyK +adcKHM1xY7Cp5sp9njqscgCDUEMmbqFni6Se0AsWD0JKdUhRQnOiw99rg8mYA4JSQej jYEFFVSyVVgGc3UUssIzgOTEsPEcKkAaAZx46JDeBRL+tgc13arlZzHTW/iiVQj5gWg7 /DjA== X-Gm-Message-State: APt69E2+aLjdAlOqQZ70AZVXBi6Xpk7tI34Tg9qo3mmqOwDxydfIhXYj Tdp8AKvjxvbBpKkV9J60/uHqdQ== X-Google-Smtp-Source: ADUXVKIqCozdHQ3PXTmEnY9Ib0yaHiQDWtoy4XOtfohK3cgqEdrM7qS0wlPPUcc6S0XL0wtXZKGWCw== X-Received: by 2002:a63:735e:: with SMTP id d30-v6mr470728pgn.257.1528746872920; Mon, 11 Jun 2018 12:54:32 -0700 (PDT) Received: from xeon-e3 (204-195-35-107.wavecable.com. [204.195.35.107]) by smtp.gmail.com with ESMTPSA id m17-v6sm65095941pgd.52.2018.06.11.12.54.32 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 11 Jun 2018 12:54:32 -0700 (PDT) Date: Mon, 11 Jun 2018 12:54:25 -0700 From: Stephen Hemminger To: Toke =?UTF-8?B?SMO4aWxhbmQtSsO4cmdlbnNlbg==?= Cc: Michel Blais , cake@lists.bufferbloat.net Message-ID: <20180611125425.792d4dcc@xeon-e3> In-Reply-To: <87wov5hzvq.fsf@toke.dk> References: <87wov5hzvq.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Cake] Bandwidith rate by host instead of global while using [dual-]srchost and [dual-]dsthost 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: Mon, 11 Jun 2018 19:54:34 -0000 On Mon, 11 Jun 2018 21:44:25 +0200 Toke H=C3=B8iland-J=C3=B8rgensen wrote: > Michel Blais writes: >=20 > > Hi all, > > > > Is it possible while using srchost, or dual-srchost, and dsthost, or > > dual-dsthost, to do a bandwidth limitation by host instead of global ? = From > > what I read, seem like not. =20 >=20 > No, not currently (as Dave said). I do believe it would be possible to > extend the current architecture to support this, though. Basically, > making the number of tins configurable to an arbitrary number and making > it possible to set individual bandwidths on them should do the trick. A > TC filter could then be used to assign traffic to the right tin based on > whatever information is available. >=20 > However, I don't think the current way of finding the next tin to > service is going to scale to an arbitrary number of tins, so this > probably needs to be changed before such a configuration is really > feasible... >=20 > -Toke Making cake into a version of HTB is not necessarily a good idea