From: David Miller <davem@davemloft.net>
To: jun.kondo@ctc-g.co.jp
Cc: linux-kernel@vger.kernel.org, omega-g1@ctc-g.co.jp,
notsuki@redhat.com, motokazu.kozaki@hp.com, htaira@redhat.com,
netdev@vger.kernel.org, tomohiko.takahashi@ctc-g.co.jp,
kotaro.sakai@ctc-g.co.jp, ken.sugawara@ctc-g.co.jp
Subject: Re: [omega-g1:11110] Re: [PATCH] net: configurable sysctl parameter "net.core.tcp_lowat" for sk_stream_min_wspace()
Date: Thu, 08 Sep 2011 22:17:46 -0400 (EDT) [thread overview]
Message-ID: <20110908.221746.534664053184784881.davem@davemloft.net> (raw)
In-Reply-To: <4E696D06.3000003@ctc-g.co.jp>
From: "Jun.Kondo" <jun.kondo@ctc-g.co.jp>
Date: Fri, 09 Sep 2011 10:33:58 +0900
> - In normal situation, acquire large default transmission
> buffer value, and ensure high throughput from the
> beginning of tcp connection
You should never do this. You should use the default buffer sizes and
as a result the kernel's TCP stack automatically adjusts the send and
receive buffers in response to the link characteristics.
When you set explicit buffer sizes, this turns off the TCP stack's
auto-tuning mechanism.
Every argument made in support of your proposed feature is based upon
a false premise of one kind of another, and this is yet another example
of this.
prev parent reply other threads:[~2011-09-09 2:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 5:38 [PATCH] net: configurable sysctl parameter "net.core.tcp_lowat" for sk_stream_min_wspace() Jun.Kondo
2011-08-15 5:47 ` David Miller
2011-08-19 9:28 ` [omega-g1:10937] " Jun.Kondo
2011-08-19 9:43 ` David Miller
2011-08-22 0:33 ` [omega-g1:11072] " Jun.Kondo
2011-08-22 14:21 ` Hagen Paul Pfeifer
2011-08-22 18:35 ` David Miller
2011-08-25 4:46 ` [omega-g1:11110] " Jun.Kondo
2011-08-25 5:00 ` David Miller
2011-09-09 1:33 ` Jun.Kondo
2011-09-09 2:17 ` David Miller [this message]
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=20110908.221746.534664053184784881.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=htaira@redhat.com \
--cc=jun.kondo@ctc-g.co.jp \
--cc=ken.sugawara@ctc-g.co.jp \
--cc=kotaro.sakai@ctc-g.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=motokazu.kozaki@hp.com \
--cc=netdev@vger.kernel.org \
--cc=notsuki@redhat.com \
--cc=omega-g1@ctc-g.co.jp \
--cc=tomohiko.takahashi@ctc-g.co.jp \
/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).