From: Rick Jones <rick.jones2@hp.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Nandita Dukkipati <nanditad@google.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, therbert@google.com, chavey@google.com,
ycheng@google.com
Subject: Re: [PATCH 1/1] TCP: increase default initial receive window.
Date: Mon, 20 Dec 2010 10:26:20 -0800 [thread overview]
Message-ID: <4D0F9FCC.7010108@hp.com> (raw)
In-Reply-To: <20101220090352.3ea7ade2@nehalam>
> Agree this is a good idea, but some further notes:
> * The control of receive window is a local function not covered by
> RFC.
> * Linux manipulates receive window automatically, unlike some other
> implementations.
>
> But any change to TCP risks breaking other broken implementations
> and users need a good way to recover.
Always good to be careful, but break in what way? Many stacks have been
advertising an initial receive window of well above 10 segments going back
literally decades.
HP-UX systems have been advertising a default/initial recieve window of 32768
bytes since the mid 1990s, Solaris systems have been advertising a default
receive window of 49152 for ages. I cannot speak to Windows' default advertised
window. While that sound a bit like "But MOM! All my friends are doing it." it
does seem to suggest that advertising an initial receive window of 10 segments
is unlikely to uncover anything new.
rick jones
next prev parent reply other threads:[~2010-12-20 18:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-18 3:20 [PATCH 1/1] TCP: increase default initial receive window Nandita Dukkipati
2010-12-18 3:59 ` Stephen Hemminger
2010-12-18 5:14 ` David Miller
2010-12-18 5:13 ` David Miller
2010-12-18 9:08 ` Nandita Dukkipati
2010-12-20 17:03 ` Stephen Hemminger
2010-12-20 18:26 ` Rick Jones [this message]
2010-12-20 18:48 ` David Miller
2010-12-21 0:15 ` [PATCH v2 " Nandita Dukkipati
2010-12-21 0:23 ` Nandita Dukkipati
2010-12-21 5:00 ` Eric Dumazet
2010-12-21 5:33 ` David Miller
2010-12-21 18:27 ` [PATCH " John Heffner
2010-12-21 18:49 ` Eric Dumazet
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=4D0F9FCC.7010108@hp.com \
--to=rick.jones2@hp.com \
--cc=chavey@google.com \
--cc=davem@davemloft.net \
--cc=nanditad@google.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=therbert@google.com \
--cc=ycheng@google.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).