From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 0FA643B29E for ; Thu, 23 Nov 2017 05:22:15 -0500 (EST) Received: from [192.168.250.101] ([134.76.241.253]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MEWPx-1eOgH91zYH-00FhMm; Thu, 23 Nov 2017 11:22:14 +0100 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Sebastian Moeller In-Reply-To: <65345DE4-8E75-4913-9FFF-2823BF70AB85@gmail.com> Date: Thu, 23 Nov 2017 11:22:13 +0100 Cc: =?utf-8?Q?Dave_T=C3=A4ht?= , Cake List Content-Transfer-Encoding: quoted-printable Message-Id: <9A62920E-9F06-443D-912E-145825EB8315@gmx.de> References: <107CB879-B196-40F1-A7C2-08B963B7A835@gmail.com> <65345DE4-8E75-4913-9FFF-2823BF70AB85@gmail.com> To: Pete Heist X-Mailer: Apple Mail (2.3273) X-Provags-ID: V03:K0:rfaukklGOPhPHDpJMDPwZcJxBMGqdoqMfOMkkVh2PLA5vQ5d/+V QnqJbrhG9dhKpYMCwkxFCeev975YmdZ+EQpbVCZrZ5x4/Pwg7oVwz1PGUUda7tByu1qf7p7 xGy0kLFCDUC2XGmq1l/mSnpMX+u2rSX26z447r/MAfO1Z8bTzVwHeqP8inxLqK6WUHzUf1P 8wWCrKVic6cqaI/dUJztA== X-UI-Out-Filterresults: notjunk:1;V01:K0:K/5Q9WRn9uQ=:cztLbUxRAtsVyCpF2yz14d uheXIH1To8iUlFHRwFO6E9qzZapxhrEepODNsBQV/eigPWYPOhcsEjdLU5Arzlqz4/EHz+H9R P40koGOqTxPKP6BTDktJAjcCKkxF73JEN+48NWzv0bZ/ILs39AFzjj+Pfn9McGjJFJWU40XIl y2qPm4qiEdD4tW3RA7Ku1PscDJ0YIXMN0SOcJh8jduIUML2kTXXR0UI/xI5R5fkxcnm1W2VX5 Hzhm38U53zQ2o0MU4clzyVYIf7v3vDiUsxy+f5D5iV224NzM/HfRYuTsxbeO4+KlhfGbTGN3l QtNhZ35cpmMypd8qEuraihVi05MWB8ludrv5HkWLmaRIZbIwe5YR71RswYNtdoCY68blKYCdy 24j/cfGjsWvRw/Eftz7Mo7HBOmMyZVmzG5fJ451zdYfezHrUjIG/M35ZiD88C0t8LKielZdsV 56PvB78EuTWTZymKeDThBBi1p9tmddxxahVKSW7xHnZ8889qvO22by3yJ5JPkntO3hx4NYy+u lmtDULJeYlXM2EtGwahTZ2wkpRsnAfpz4TdMbRfQ9xmxfnEYs92GTjUwPUkmAAEal0dgFhvTp R1t+Y7x3ijCGdm8ugIRHR9hEIhwIJZHyywPvTMIrjAx2NPZzEMHe1dm0F5pXw6qJQtwW1eWIM ZLr98Aww95oVUtHqZRl4V/n1xiCwNuqbxmEgiDHNBynmuSZOaDvYVIfYPsfViQjTfPKZI4kpI YkwvmcmKh7flBlPBg0S7L3c7+KCzZxS7kyEIF+8E0eTuOoy954xSFMQ7iBYO7CeFxdy+CRgZn BRcXS2EvfWM+IdMadGj2p9Z+L+BLxuB3BDvPJoRfrcbuWITdkU= Subject: Re: [Cake] small cake_hash optimization? 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, 23 Nov 2017 10:22:16 -0000 Hi Pete, > On Nov 23, 2017, at 10:30, Pete Heist wrote: >=20 >=20 >> On Nov 23, 2017, at 9:00 AM, Sebastian Moeller = wrote: >>=20 >> Hi Pete, >>=20 >> I should have mentioned "overhead 64 mpu 84" only make sense in = combination with a shaper limit (well, they will make sure the cake = statistics will be more reflective of what is happening on the ethernet = wire, but I am not sure whether that is worth the run-time cost the = overhead calculation incurs). >>=20 >> Somewhat unrelated, I wondered about all the excitement about irtt = and cloned the repository to my mac, and was absolutely delighted to = realize that irtt will also effortlessly work under macos. I only have = run the demo from the readme.md with both client and server running at = the same machine, but I got results that look reasonable on first sight = (but I admit I really do not know exact;y what to expect). This is = really great! >=20 > Thanks for the overhead info. I used that in my latest tests. That = makes me wonder if those overheads could be defaulted when Cake knows = Ethernet is being used with rate limiting? I know a goal is to make cake = easier to configure so such things are examples of what people are = likely to miss. Well, as you note later cake really has no idea what the user = wants unless the user actually explicitly requests it. But in your case, = I believe instead of the explicit "overhead 38 mpu 84" (I note the 64 = above is a typo) you could use the "ethernet" keyword which will under = the hood expand to the same values. Personally I am not a big friend of = the keywords, but even I admit that they help users lacking the time to = dive into the details, especially if the name is as obvious as = "ethernet" (all I would wish though would be that these keywords wouls = still need to be lead by the "overhead" command, so "overhead ethernet" = instead of "ethernet", because that IMHO would be more explicit, but I = digress). Please note that I currently have issues with overhead accounting with = on dave's cobalt branch and the new iproute2 tools, automatic kernel = overhead accounting does not seem to work at all, so could you please = post the output of: tc -s qdisc after one of your experiments to confirm that the requested overhead was = actually applied? >=20 > Glad to hear irtt runs for you! I was waiting to post something until = I clean up some more things in the todo list, but since you found it, = let me know (file an Issue) if you find any problems. Also, if you have = something later than El Capitan, I might be interested to see the output = from =E2=80=9Cirtt sleep=E2=80=9D or ten seconds or so from =E2=80=9Cirtt = clock=E2=80=9D, as I=E2=80=99m gradually learning about timer/clock = behavior on different OSs. I guess it could also be filed as an Issue, = so we don=E2=80=99t add too much to the cake list... As I am currently on 10.12.6 Sierra, I just went and created two new = issues with the requested information; I should note this is a = pre-fancy-oled-replacement-for-function-keys macbook pro with a quad 2.5 = GHz i7 cpu. Best Regards Sebastian=