From: David Miller <davem@davemloft.net>
To: rick.jones2@hp.com
Cc: shemminger@vyatta.com, nanditad@google.com,
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:48:14 -0800 (PST) [thread overview]
Message-ID: <20101220.104814.59687502.davem@davemloft.net> (raw)
In-Reply-To: <4D0F9FCC.7010108@hp.com>
From: Rick Jones <rick.jones2@hp.com>
Date: Mon, 20 Dec 2010 10:26:20 -0800
>> 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.
Agreed.
next prev parent reply other threads:[~2010-12-20 18:47 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
2010-12-20 18:48 ` David Miller [this message]
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=20101220.104814.59687502.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chavey@google.com \
--cc=nanditad@google.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--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).