netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: John Heffner <jheffner@psc.edu>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] apply cwnd rules to FIN packets with data
Date: Mon, 05 Feb 2007 16:20:14 -0800	[thread overview]
Message-ID: <45C7C9BE.5050205@hp.com> (raw)
In-Reply-To: <45C7C79D.1070707@psc.edu>

John Heffner wrote:
> 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?

Is the cwnd in the stack byte based, or packet based?

While "all" the RFCs tend to discuss things in terms of byte-based cwnds 
and assumptions based on MSSes and such, the underlying principle was/is 
a conservation of packets.  As David said, a packet is a packet, and if 
one were going to be sending a FIN segment, it might as well carry data. 
  And if one isn't comfortable sending that one last data segment with 
the FIN because cwnd wasn't large enough at the time, should the FIN be 
sent at that point, even if it is waffer thin?

rick jones
2 cents tossed-in from the peanut gallery

  reply	other threads:[~2007-02-06  0:20 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 [this message]
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=45C7C9BE.5050205@hp.com \
    --to=rick.jones2@hp.com \
    --cc=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).