From: John Heffner <jheffner@psc.edu>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] apply cwnd rules to FIN packets with data
Date: Mon, 05 Feb 2007 19:11:09 -0500 [thread overview]
Message-ID: <45C7C79D.1070707@psc.edu> (raw)
In-Reply-To: <20070205.150815.112291591.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
David Miller wrote:
>> However, I can't think of any reason why the cwnd test should not
>> apply.
>
> Care to elaborate here? You can view the FIN special case as an off
> by one error in the CWND test, it's not going to melt the internet.
> :-)
True, it's not going to melt the internet, but why stop at one when two
would finish the connection even faster? Not sure I buy this argument.
Was there some benchmarking data that was a justification for this in
the first place?
My first patch was broken anyway (should not have pulled the test from
tso_should_defer), and the change is not needed to the nagle test since
it's implicit. This patch just restores the old behavior from before
TSO, sending the FIN when it's the last true segment. We can debate the
merits of applying congestion control to the FIN separately. :)
-John
[-- Attachment #2: fin_cwnd1.patch --]
[-- Type: text/plain, Size: 963 bytes --]
Don't apply FIN exception to full TSO segments.
Signed-off-by: John Heffner <jheffner@psc.edu>
---
commit 89de0d8cb75958b0315c076b31a597143e30f7a4
tree 7e9c321e62729c6ef76e3886fe9edf2ac78a680c
parent c0d4d573feed199b16094c072e7cb07afb01c598
author John Heffner <jheffner@psc.edu> Mon, 05 Feb 2007 18:42:31 -0500
committer John Heffner <jheffner@psc.edu> Mon, 05 Feb 2007 18:42:31 -0500
net/ipv4/tcp_output.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c
index 975f447..58b7111 100644
--- a/net/ipv4/tcp_output.c
+++ b/net/ipv4/tcp_output.c
@@ -965,7 +965,8 @@ static inline unsigned int tcp_cwnd_test
u32 in_flight, cwnd;
/* Don't be strict about the congestion window for the final FIN. */
- if (TCP_SKB_CB(skb)->flags & TCPCB_FLAG_FIN)
+ if ((TCP_SKB_CB(skb)->flags & TCPCB_FLAG_FIN) &&
+ tcp_skb_pcount(skb) == 1)
return 1;
in_flight = tcp_packets_in_flight(tp);
next prev parent reply other threads:[~2007-02-06 0:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 21:58 [PATCH] apply cwnd rules to FIN packets with data John Heffner
2007-02-05 22:56 ` David Miller
2007-02-05 23:02 ` John Heffner
2007-02-05 23:08 ` David Miller
2007-02-06 0:11 ` John Heffner [this message]
2007-02-06 0:20 ` Rick Jones
2007-02-06 0:25 ` John Heffner
2007-02-06 1:54 ` David Miller
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=45C7C79D.1070707@psc.edu \
--to=jheffner@psc.edu \
--cc=davem@davemloft.net \
--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).