From: Rick Jones <rick.jones2@hp.com>
To: Cong Wang <amwang@redhat.com>
Cc: David Laight <David.Laight@ACULAB.COM>,
netdev@vger.kernel.org, Ben Greear <greearb@candelatech.com>,
David Miller <davem@davemloft.net>,
Eric Dumazet <eric.dumazet@gmail.com>,
Stephen Hemminger <shemminger@vyatta.com>,
Thomas Graf <tgraf@redhat.com>
Subject: Re: TCP delayed ACK heuristic
Date: Wed, 19 Dec 2012 10:39:37 -0800 [thread overview]
Message-ID: <50D209E9.2000504@hp.com> (raw)
In-Reply-To: <1355900436.6665.16.camel@cr0>
On 12/18/2012 11:00 PM, Cong Wang wrote:
> On Tue, 2012-12-18 at 16:39 +0000, David Laight wrote:
>> There are problems with only implementing the acks
>> specified by RFC1122.
>
> Yeah, the problem is if we can violate this RFC for getting better
> performance. Or it is just a no-no?
>
> Although RFC 2525 mentions this as "Stretch ACK Violation", I am still
> not sure if that means we can violate RFC1122 legally.
The term used in RFC1122 is "SHOULD" not "MUST." Same for RFC2525 when
it talks about "Stretch ACK Violation." A TCP stack may have behaviour
which differs from a SHOULD so long as there is a reasonable reason for it.
rick jones
next prev parent reply other threads:[~2012-12-19 18:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <270756364.27707018.1355842632348.JavaMail.root@redhat.com>
2012-12-18 15:11 ` TCP delayed ACK heuristic Cong Wang
2012-12-18 16:30 ` Eric Dumazet
2012-12-19 6:54 ` Cong Wang
2012-12-18 16:39 ` David Laight
2012-12-18 17:54 ` Rick Jones
2012-12-19 9:52 ` David Laight
2012-12-19 7:00 ` Cong Wang
2012-12-19 18:39 ` Rick Jones [this message]
2012-12-19 20:59 ` David Miller
2012-12-20 3:23 ` Cong Wang
2012-12-20 9:57 ` David Laight
2012-12-20 12:41 ` Cong Wang
2012-12-19 23:08 ` 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=50D209E9.2000504@hp.com \
--to=rick.jones2@hp.com \
--cc=David.Laight@ACULAB.COM \
--cc=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=tgraf@redhat.com \
/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).