From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Komuro <komurojun-mbn@nifty.com>
Cc: shemminger@linux.foundation.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [NOT VERY SAFE] [TCP]: Set initial_ssthresh default to zero in Cubic and BIC.
Date: Mon, 15 Oct 2007 08:55:41 -0700 [thread overview]
Message-ID: <20071015085541.48ec63ae@freepuppy.rosehill> (raw)
In-Reply-To: <20071015215949.50399c00.komurojun-mbn@nifty.com>
On Mon, 15 Oct 2007 21:59:49 +0900
Komuro <komurojun-mbn@nifty.com> wrote:
> Dear shemminger
>
> >In which case it is zero because that is the default value.
>
> The default value of snd_ssthresh is 0x7fffffff, isn't it?
>
> [linux/net/ipv4/tcp_ipv4.c]
> static int tcp_v4_init_sock(struct sock *sk)
> ...
> tp->snd_ssthresh = 0x7fffffff; /* Infinity */
> ...
>
> Best Regards
> Komuro
>
>
Yes that value means that TCP stays in slow start until the first loss.
This makes TCP behave as expected in the RFC's.
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-10-15 15:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071006132601.f944f461.komurojun@nifty.com>
[not found] ` <20071014073658.d4352b8c.komurojun@nifty.com>
2007-10-13 22:52 ` [NOT VERY SAFE] [TCP]: Set initial_ssthresh default to zero in Cubic and BIC David Miller
2007-10-13 22:54 ` David Miller
[not found] ` <20071014100245.914b784a.komurojun@nifty.com>
2007-10-14 4:28 ` Komuro
2007-10-14 4:32 ` David Miller
2007-10-14 4:53 ` Komuro
2007-10-14 5:23 ` David Miller
2007-10-15 12:59 ` Komuro
2007-10-15 15:55 ` Stephen Hemminger [this message]
[not found] ` <20080302210716.69727582.komurojun-mbn@nifty.com>
2008-03-02 12:27 ` [BUG kernel 2.6.25-rc3 IPV6] ping6 -I eth0 ff02::1 causes system hang YOSHIFUJI Hideaki / 吉藤英明
2008-03-03 22:06 ` Komuro
2008-03-04 17:49 ` Brian Haley
2008-03-04 7:40 ` Andrew Morton
2008-03-08 4:44 ` Komuro
2008-03-08 5:20 ` Komuro
2008-03-08 11:56 ` 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=20071015085541.48ec63ae@freepuppy.rosehill \
--to=shemminger@linux-foundation.org \
--cc=komurojun-mbn@nifty.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux.foundation.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).