From: hiren panchasara <hiren@strugglingcoder.info>
To: netdev@vger.kernel.org
Subject: RACK not getting disabled
Date: Mon, 18 Sep 2017 13:14:28 -0700 [thread overview]
Message-ID: <20170918201428.GB28186@strugglingcoder.info> (raw)
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
Hi all, I am trying to disable rack to see 3dupacks in action during
loss-detection but based on the pcap, I see that it's still trigger
loss-recovery on the first SACK (as if RACK is still enabled/active).
Here is what I did to disable rack:
net.ipv4.tcp_recovery = 0
I've also disabled metrics:
net.ipv4.tcp_no_metrics_save = 1
And also flushed existing entries with 'ip tcp_metrics flush' just to be
on a safer side.
Not really relevant here but I've also switched to reno.
I am on: 4.10.0-33-generic
pcap: https://transfer.sh/mfoiN/reno_no_rack.pcap
What am I missing? I can provide any additional info.
Cheers,
Hiren
[-- Attachment #2: Type: application/pgp-signature, Size: 603 bytes --]
next reply other threads:[~2017-09-18 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 20:14 hiren panchasara [this message]
2017-09-18 21:18 ` RACK not getting disabled Eric Dumazet
2017-09-18 21:29 ` hiren panchasara
2017-09-18 21:45 ` hiren panchasara
2017-09-18 21:46 ` Yuchung Cheng
2017-09-18 21:55 ` hiren panchasara
2017-09-18 22:05 ` Yuchung Cheng
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=20170918201428.GB28186@strugglingcoder.info \
--to=hiren@strugglingcoder.info \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).