From: David Miller <davem@davemloft.net>
To: jheffner@psc.edu
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] apply cwnd rules to FIN packets with data
Date: Mon, 05 Feb 2007 17:54:04 -0800 (PST) [thread overview]
Message-ID: <20070205.175404.23014614.davem@davemloft.net> (raw)
In-Reply-To: <45C7C79D.1070707@psc.edu>
From: John Heffner <jheffner@psc.edu>
Date: Mon, 05 Feb 2007 19:11:09 -0500
> 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. :)
Yes, let's split one hair at a time :-)
Patch applied, thanks John. I'll push this to the 2.6.x -stable
branch too.
prev parent reply other threads:[~2007-02-06 1:54 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
2007-02-06 0:20 ` Rick Jones
2007-02-06 0:25 ` John Heffner
2007-02-06 1:54 ` 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=20070205.175404.23014614.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jheffner@psc.edu \
--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).