netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Heffner <jheffner@psc.edu>
To: Rick Jones <rick.jones2@hp.com>
Cc: "Baruch Even" <baruch@ev-en.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>,
	"David Miller" <davem@davemloft.net>,
	Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] [TCP] Sysctl: document tcp_max_ssthresh (Limited	Slow-Start)
Date: Fri, 18 May 2007 16:49:08 -0400	[thread overview]
Message-ID: <464E1144.4010806@psc.edu> (raw)
In-Reply-To: <464E00E5.5050801@hp.com>

Rick Jones wrote:
> as an asside, "tcp_max_ssthresh" sounds like the maximum value ssthresh 
> can take-on.  is that correct, or is this more of a "once ssthresh is 
> above this, behave in this new way?"  If that is the case, while the 

I don't like it either, but you'll have to talk to Sally Floyd about 
that one.. ;)

In general, I would like the documentation to emphasize more how to set 
the parameter than describe the algorithm.  The max_ssthresh parameter 
should ideally be set to the bottleneck queue size, or more 
realistically a conservative value that's likely to be smaller than the 
bottleneck queue size.  When max_ssthresh is smaller than the bottleneck 
queue, (limited) slow start will not overflow it until cwnd has fully 
ramped up to the appropriate size.

   -John

  reply	other threads:[~2007-05-18 20:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 16:27 [PATCH] [TCP] Sysctl: document tcp_max_ssthresh (Limited Slow-Start) Ilpo Järvinen
2007-05-18 17:42 ` Baruch Even
2007-05-18 19:39   ` Rick Jones
2007-05-18 20:49     ` John Heffner [this message]
2007-05-19  7:24       ` Ilpo Järvinen
2007-05-19  7:32     ` Ilpo Järvinen
2007-05-19  7:01   ` Ilpo Järvinen
2007-05-19  7:26     ` Ilpo Järvinen

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=464E1144.4010806@psc.edu \
    --to=jheffner@psc.edu \
    --cc=baruch@ev-en.org \
    --cc=davem@davemloft.net \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=netdev@vger.kernel.org \
    --cc=rick.jones2@hp.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).