From: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
To: netdev@vger.kernel.org
Subject: Shaping TCP ACK packets
Date: Mon, 05 Dec 2011 23:18:03 -0500 (EST) [thread overview]
Message-ID: <7cf7b0f6-b30f-465a-9e50-20bd2c31bbe9@jasiiieee> (raw)
In-Reply-To: <b7c7ae97-0030-4397-a1e3-ec29babdff4d@jasiiieee>
Hello, all. I've seen several sites recommend prioritizing TCP ACK packets using tc. Is that a good idea? I have two reservations:
1) If my line is congested, isn't delaying ACKs a good way to slow down the conversation? Accelerating ACKs under congestion sounds a bit like stuffing more food in my mouth when I'm already choking.
2) By messing with normal coordination of TCP, do I risk making a mess. Specifically, can I create problems with out of order packet delivery - send an ACK before the packet which should have preceded it? I suppose in a well behaved protocol that wouldn't happen but I'm not sure. Thanks - John
next parent reply other threads:[~2011-12-06 3:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b7c7ae97-0030-4397-a1e3-ec29babdff4d@jasiiieee>
2011-12-06 4:18 ` John A. Sullivan III [this message]
2011-12-06 5:59 ` Shaping TCP ACK packets Eric Dumazet
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=7cf7b0f6-b30f-465a-9e50-20bd2c31bbe9@jasiiieee \
--to=jsullivan@opensourcedevel.com \
--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