From: "David S. Miller" <davem@davemloft.net>
To: "Meda, Prasanna" <pmeda@akamai.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com, davem@redhat.com
Subject: Re: rcv_wnd = init_cwnd*mss
Date: Thu, 28 Oct 2004 16:56:58 -0700 [thread overview]
Message-ID: <20041028165658.753eee50.davem@davemloft.net> (raw)
In-Reply-To: <DB2C167D8FFDEA45B8FC0B1B75E3EE154A3B08@usca1ex-priv1.sanmateo.corp.akamai.com>
On Wed, 27 Oct 2004 23:15:48 -0700
"Meda, Prasanna" <pmeda@akamai.com> wrote:
> Thanks, still it is unclear to me why are we
> downsizing the advertised window(rcv_wnd) to cwnd?
> To defeat disobeying sender, or something like below?
There is never any reason to advertise a receive window
larger than the initial congestion window of the sender
could ever be.
Setting it properly like this also makes sure that we do
receive window update events at just the right place as
the sender starts sending us the initial data frames.
> And also in the following line,
> if (*rcv_wscale && sysctl_tcp_app_win && space>=mss &&
> space - max((space>>sysctl_tcp_app_win), mss>>*rcv_wscale) <
> 65536/2)
>
> space is actual_space>>rcv_wscale, mss is actual value.
> Why are we checking space>=mss, which are in different
> scales? The second line is doing max on space and mss
> on same scales, and looks right.
Yep, that space>=mss test looks super buggy for the *rcv_wscale
not zero case.
Good thing we don't have this buggy code in 2.6.x any more.
It's only present in 2.4.x
next prev parent reply other threads:[~2004-10-28 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 6:15 rcv_wnd = init_cwnd*mss Meda, Prasanna
2004-10-28 23:56 ` David S. Miller [this message]
2004-10-29 0:55 ` Prasanna Meda
-- strict thread matches above, loose matches on Subject: below --
2004-10-28 5:14 Meda, Prasanna
2004-10-28 5:21 ` David S. 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=20041028165658.753eee50.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pmeda@akamai.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).