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 983153B2A4 for ; Fri, 24 Nov 2017 14:41:39 -0500 (EST) Received: by mail-wr0-x22e.google.com with SMTP id o14so21210217wrf.9 for ; Fri, 24 Nov 2017 11:41:39 -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:message-id:references :to; bh=OPX8VPMcOKkTPX74pb2ZBVilzRpTmyFanNFp0Iq62Io=; b=TnabdrP800VPklczdyj/15pwRwbhWaFhIixQJ2TdXGUx5q3g/aL3qeTFIrynzPegAw Ni6pnFxvBHwGbBVVcw91Qjtc9O2NA7HTIpdSoEU9WyxjKWCgDlo4PCTwEpWvc7UcRQVO /4E3MiCD0TiTI7mXn7wmzl9XssoFjo20qODQLQklk1NUiwEhQ0C2UzMmDLY2zjyJu7Gq 4rL45d3c3AqPPcYHg1VuYAOH+uswUV9JPcaBkTPjEr1qZMDgFt42eJbU97LIxs+NaWb3 dkjdHDILAVspcr/t+k2o7hXrRb4q7oKqDUZDXEG33AU9vleUV6PO45uZqH2gb7D2ikLx LVbw== 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 :message-id:references:to; bh=OPX8VPMcOKkTPX74pb2ZBVilzRpTmyFanNFp0Iq62Io=; b=Kn3hXiNTtreN/TkT/mTHxpsizpAUD59UMoiduj3PK0m467kc2R1v6ct7HRiXu+3iRx HlrZxJFtKMCKU9oiQ/owyRDX3Y27frNJQGBQD9VXM2+vIr1EbvFHGOsADlDHL00/aFA4 Mi3vvuuGs7lsemwVukwTfMLmfOiZk5h1JLeMb8RtulR9m5/GorgGpoZST1RjGYIwTxKb bJ3lMdWbXjH0oynFmyGmYbJY0ooFgJStlSrC3l/kjnD3mIbYbGT0HuXmy/cWdhyMX0ZY Cy4V4Ms+TZbUmoYzVuuXzPqK/aNE0K7geTqnpT+dVgM4bKwLjiajAO4vdQxZXOZ3g/aF 2UDA== X-Gm-Message-State: AJaThX4gNkE6pELjpky7LZqJAw8/3HnMmpKe0Bw04VwtZppsmVT2rGY/ y2/WatSWo0h8Ojq0vhasSgM= X-Google-Smtp-Source: AGs4zMZBDSa78VGZgpJ696cKlbUb624xQ4J8rJYGaPgrH3gVSPIwkz5J+VwwFFo9fLG9S8M/tbdM4Q== X-Received: by 10.223.197.131 with SMTP id m3mr27342773wrg.0.1511552498656; Fri, 24 Nov 2017 11:41:38 -0800 (PST) Received: from [10.72.0.130] (h-1169.lbcfree.net. [185.99.119.68]) by smtp.gmail.com with ESMTPSA id v18sm14891345wrv.37.2017.11.24.11.41.37 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 24 Nov 2017 11:41:37 -0800 (PST) Content-Type: multipart/alternative; boundary="Apple-Mail=_C3231B6F-5784-405A-80AD-E6C20D828622" Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Pete Heist In-Reply-To: <0D339F2F-F2CB-4800-84B9-E7321AE4D15E@gmail.com> Date: Fri, 24 Nov 2017 20:41:36 +0100 Cc: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= , Cake List Message-Id: References: <71FB183D-F848-4513-A6F6-D03FD0F10769@gmail.com> <52C2B216-220C-4C17-882C-9994867E86BB@gmail.com> <87tvxlvsex.fsf@nemesis.taht.net> <87609zapmt.fsf@toke.dk> <0D339F2F-F2CB-4800-84B9-E7321AE4D15E@gmail.com> To: Dave Taht X-Mailer: Apple Mail (2.3124) Subject: Re: [Cake] lan keyword affects host fairness 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, 24 Nov 2017 19:41:39 -0000 --Apple-Mail=_C3231B6F-5784-405A-80AD-E6C20D828622 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Nov 24, 2017, at 2:49 PM, Pete Heist wrote: >=20 > Removing the bandwidth keywords altogether and going back to = fq_codel=E2=80=99s specification of target and interval would be my = personal preference (unless we can figure out how to make the keywords = work well with one another in all cases). To add to my comments, this probably came across as too harsh or = discontinuous an idea at this stage when we=E2=80=99re in the process of = shoring things up- that wasn=E2=80=99t my intent! There is the other side that these keywords save people from having to = know more. Which is better, explaining target and interval to everyone = or having them use these? I imagine that was the logic that went into = it. Also, if it=E2=80=99s not a good idea to be changing the = configuration interface at this point (and it may not be), then there = are alternatives, and the man page addition will definitely help people. = Maybe I=E2=80=99ll make some runs across a range of rtts to understand = this better=E2=80=A6 --Apple-Mail=_C3231B6F-5784-405A-80AD-E6C20D828622 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
On Nov 24, 2017, at 2:49 PM, Pete Heist <peteheist@gmail.com>= wrote:

Removing the = bandwidth keywords altogether and going back to fq_codel=E2=80=99s = specification of target and interval would be my personal preference = (unless we can figure out how to make the keywords work well with one = another in all cases).

To add to my comments, this probably came across = as too harsh or discontinuous an idea at this stage when we=E2=80=99re = in the process of shoring things up- that wasn=E2=80=99t my = intent!

There is the other side that = these keywords save people from having to know more. Which is better, = explaining target and interval to everyone or having them use these? I = imagine that was the logic that went into it. Also, if it=E2=80=99s not = a good idea to be changing the configuration interface at this point = (and it may not be), then there are alternatives, and the man page = addition will definitely help people. Maybe I=E2=80=99ll make some runs = across a range of rtts to understand this better=E2=80=A6

= --Apple-Mail=_C3231B6F-5784-405A-80AD-E6C20D828622--