From: David Miller <davem@davemloft.net>
To: jmaxwell37@gmail.com
Cc: kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
kaber@trash.net, edumazet@google.com, ncardwell@google.com,
ycheng@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, jmaxwell@redhat.com
Subject: Re: [PATCH net-next] tcp: v1 always send a quick ack when quickacks are enabled
Date: Thu, 09 Jul 2015 14:16:18 -0700 (PDT) [thread overview]
Message-ID: <20150709.141618.71467123946708533.davem@davemloft.net> (raw)
In-Reply-To: <1436314348-25577-1-git-send-email-jmaxwell37@gmail.com>
From: Jon Maxwell <jmaxwell37@gmail.com>
Date: Wed, 8 Jul 2015 10:12:28 +1000
> V1 of this patch contains Eric Dumazet's suggestion to move the per
> dst RTAX_QUICKACK check into tcp_in_quickack_mode(). Thanks Eric.
>
> I ran some tests and after setting the "ip route change quickack 1"
> knob there were still many delayed ACKs sent. This occured
> because when icsk_ack.quick=0 the !icsk_ack.pingpong value is
> subsequently ignored as tcp_in_quickack_mode() checks both these
> values. The condition for a quick ack to trigger requires
> that both icsk_ack.quick != 0 and icsk_ack.pingpong=0. Currently
> only icsk_ack.pingpong is controlled by the knob. But the
> icsk_ack.quick value changes dynamically depending on heuristics.
> The crux of the matter is that delayed acks still cannot be entirely
> disabled even with the RTAX_QUICKACK per dst knob enabled. This
> patch ensures that a quick ack is always sent when the RTAX_QUICKACK
> per dst knob is turned on.
>
> The "ip route change quickack 1" knob was recently added to enable
> quickacks. It was modeled around the TCP_QUICKACK setsockopt() option.
> This issue is that even with "ip route change quickack 1" enabled
> we still see delayed ACKs under some conditions. It would be nice
> to be able to completely disable delayed ACKs.
...
> The issue is that both the "ip route change quickack 1" knob and
> the TCP_QUICKACK option set the icsk_ack.pingpong variable to 0.
> However at the business end in the __tcp_ack_snd_check() routine,
> tcp_in_quickack_mode() checks that both icsk_ack.quick != 0
> and icsk_ack.pingpong=0 in order to trigger a quickack. As
> icsk_ack.quick is determined by heuristics it can be 0. When
> that occurs the icsk_ack.pingpong value is ignored and a delayed
> ACK is sent regardless.
>
> This patch moves the RTAX_QUICKACK per dst check into the
> tcp_in_quickack_mode() routine which ensures that a quickack is
> always sent when the quickack knob is enabled for that dst.
>
> Signed-off-by: Jon Maxwell <jmaxwell37@gmail.com>
Looks good, applied, thanks Jon.
prev parent reply other threads:[~2015-07-09 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 0:12 Jon Maxwell
2015-07-09 21:16 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150709.141618.71467123946708533.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jmaxwell37@gmail.com \
--cc=jmaxwell@redhat.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®