From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vk1-xa33.google.com (mail-vk1-xa33.google.com [IPv6:2607:f8b0:4864:20::a33]) (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 E586E3B2A4 for ; Fri, 8 May 2020 02:36:48 -0400 (EDT) Received: by mail-vk1-xa33.google.com with SMTP id k25so157186vkn.2 for ; Thu, 07 May 2020 23:36:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NRiKAwxUo7O0e62HFUVakBcIiFSW6BQZ2pG04+qHgzc=; b=oqldGGTpoHUtkz6SDWOvHUMRse7OxCOyRoS4EYdQEzSFKZmFvtfD4Tv8byMX87RhZo mnENX1E9Rt7K/REx4+ZMuvSmmczMRq8j0NsPICFo3Cb6msDY5LZBo8Bk7gmZ2F6B3kKz q2UEMLAY+MYRmiAf5jxb19Zf6RgVlCT4ECsktVdk5a1rJYv5bOb16rPxTO0h0UZE+P/i Kc9I0tnBq5FuORsyCDzsunSF55pgv9fsc65dN1B9iPHEnl31TNRuYnp9MSKJ10ByYCY+ 7+Z4rbDey0fLRGn2v4ehNi7IxdQlWR362MC/MpGFTr/02xgc0kcQQQ+mO3p/BbtSr5cG fbHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NRiKAwxUo7O0e62HFUVakBcIiFSW6BQZ2pG04+qHgzc=; b=piWWhxZjd4Nl5D3Zc7U5mdjli31x/05hgcTK6UUg3BQYyakAjGFT1SIOx9TWiFv3mn hU6wP1JVZG+KKl8L2fLY4rB/tdu0Wglb8hDzbzfmV1m4CcWMKT2qvqMA8Q9NKKDM1/hJ ZuIFtn//ub/bRL2B+2PfN7+TTmIBR9Vp5zSvp8+Q+ui5T3ql5H8tHbovQ8NM0Zv+DAXc ldTPSWADFcb9COXD9KXU11f3SpPgopV9Im0tFqQ7AdBKei7dwdXiL3mBST0XmKTcZkax zWwzMmYuEvDhd4tZhjfloBkWDsCATFYUndTUggzNK2QDl+apV1inF3EMAIHpsCU+0HbY m9vw== X-Gm-Message-State: AGi0PuYwqup0XkgSMqYAk59T8WKPlvUsJnFjHHvyShzfyMSoBCEomxS7 mg5D7cYonx7fSKMTiS50PTMU1K85m6se977f/IA= X-Google-Smtp-Source: APiQypLTNUWj1nfamqCkthY9N36DjPgOH7dWZG2vq1syKICDmD/vVbh1Uby/Hlwi4mRUiu/bEIfWplfSM0Wa9EvYZ1w= X-Received: by 2002:a05:6122:4a:: with SMTP id q10mr579498vkn.47.1588919808351; Thu, 07 May 2020 23:36:48 -0700 (PDT) MIME-Version: 1.0 References: <87wo5okhbo.fsf@toke.dk> In-Reply-To: From: Avakash bhat Date: Fri, 8 May 2020 12:06:32 +0530 Message-ID: To: Sebastian Moeller Cc: cake@lists.bufferbloat.net, =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= , Vybhav Pai , Shrinidhi Varna , "Mohit P. Tahiliani" , Deepak K Content-Type: multipart/alternative; boundary="000000000000c0e0e805a51d385b" Subject: Re: [Cake] Query on ACK 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, 08 May 2020 06:36:49 -0000 --000000000000c0e0e805a51d385b Content-Type: text/plain; charset="UTF-8" Ok thanks so much for the clarifications. That cleared it up quite a bit. Thanks, Avakash Bhat On Thu, May 7, 2020 at 12:37 PM Sebastian Moeller wrote: > I think that you will remove all redundant Backs in one go considerably > advancing the new ACK in the queue. And more importantly, in most relevant > modes cake will apply one queue per flow stochastically, so almost all > packet's in a reverse ACK flow will be ACK with identical 5-tupel.... > > On 7 May 2020 08:44:59 CEST, Avakash bhat wrote: >> >> >> Thanks for the quick response. I also had a followup question. >> >> If the ack filter adds the new ack to the tail of the queue after >> removing an ack from the queue, won't it be starving the ack? >> The replaced ack was much ahead in the queue than the ack we replaced at >> the tail right? >> >> Thanks, >> Avakash Bhat >> > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > --000000000000c0e0e805a51d385b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Ok thanks so much for the clarifications.=C2=A0
That c= leared=C2=A0it up quite a bit.=C2=A0

Thanks,= =C2=A0
Avakash Bhat

On Thu, May 7, 2020 at 12:37 PM Se= bastian Moeller <mo= eller0@gmx.de> wrote:
I think that you will remove all redundant Backs in one g= o considerably advancing the new ACK in the queue. And more importantly, in= most relevant modes cake will apply one queue per flow stochastically, so = almost all packet's in a reverse ACK flow will be ACK with identical 5-= tupel....

On 7 May 2020 08:44:59 CEST, Av= akash bhat <av= akash261@gmail.com> wrote:

Thanks for the quick response. I also had a followup q= uestion.=C2=A0

If the ack filter adds the new ack to the tail = of the queue after removing an ack from the queue, won't it be starving= the ack?=C2=A0
The replaced ack was much ahead in the queue than= the ack we replaced at the tail right?

Thanks,
Avakash Bhat

--
Sent from my Android device with K-9 Mail. Pl= ease excuse my brevity.
--000000000000c0e0e805a51d385b--