From dave.taht at gmail.com Mon Apr 10 22:12:12 2023 From: dave.taht at gmail.com (Dave Taht) Date: Mon, 10 Apr 2023 19:12:12 -0700 Subject: [Codel] =?utf-8?q?ACM_queue_article_on_facebook=C2=B4s_=22Adaptiv?= =?utf-8?q?e_LIFO=22_and_codel?= Message-ID: I have no idea what an "adaptive LIFO" is, but the acm queue paper here just takes the defaults from codel... https://twitter.com/teivah/status/1645362443986640896 And a go implementation of codel for queues in general has appeared here: https://github.com/joshbohde/codel -- AMA March 31: https://www.broadband.io/c/broadband-grant-events/dave-taht Dave Täht CEO, TekLibre, LLC From chromatix99 at gmail.com Mon Apr 10 22:41:07 2023 From: chromatix99 at gmail.com (Jonathan Morton) Date: Tue, 11 Apr 2023 05:41:07 +0300 Subject: [Codel] =?utf-8?q?ACM_queue_article_on_facebook=C2=B4s_=22Adaptiv?= =?utf-8?q?e_LIFO=22_and_codel?= In-Reply-To: References: Message-ID: <541FD0C8-4BAF-47D1-93F8-7C5A879ADF23@gmail.com> > On 11 Apr, 2023, at 5:12 am, Dave Taht wrote: > > I have no idea what an "adaptive LIFO" is, but the acm queue paper > here just takes the defaults from codel... > > https://twitter.com/teivah/status/1645362443986640896 They're applying it to a server request queue, not a network packet queue. I can see the logic of it in that context, but I would also note that LIFO breaks one of Codel's core assumptions, which is that the maximum delay of the queue it's controlling can be inferred from the delay experienced by the most recently dequeued item. Maybe it still happens to work by accident, or maybe they've implemented some specific workaround, but that paper is a very high-level overview (of more than one technology, to boot) without much technical detail. If I didn't already know a great deal about Codel from the coal face, I wouldn't even know to consider such a failure mode, let alone be able to infer what they could do to mitigate it. - Jonathan Morton