From: Ben Greear <greearb@candelatech.com>
To: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
Cc: David Miller <davem@davemloft.net>,
rick.jones2@hp.com, netdev@vger.kernel.org
Subject: Re: Question on TSO maximum segment sizes.
Date: Thu, 11 Oct 2007 17:17:48 -0700 [thread overview]
Message-ID: <470EBD2C.8020704@candelatech.com> (raw)
In-Reply-To: <D5C1322C3E673F459512FB59E0DDC32903C440EE@orsmsx414.amr.corp.intel.com>
Waskiewicz Jr, Peter P wrote:
>> From: Rick Jones <rick.jones2@hp.com>
>> Date: Thu, 11 Oct 2007 16:50:46 -0700
>>
>>> For just messing about, might it be possible to tweak the socket
>>> buffer sizes and tcp_tso_win_divisor to kludge things for a short
>>> while? Couldn't ship that way certainly, but assuming
>> Peter's going
>>> to get his broken hardware fixed it might let him limp
>> along until then.
>>
>> TCP dynamically grows the socket buffer sizes unless the
>> application explicitly sets them via setsockopt() and the
>> limits imposed in those cases are controlled by
>> tcp_{,r,w}mem[] sysctls. Decreasing those will kill
>> performance exactly for the cases this person cares about.
I just tried turning off my explicit SO_SNDBUF/SO_RCVBUG settings in my app,
and the connection ran very poorly through a link with even a small
bit of latency (~2-4ms I believe).
It ran near gige line speed through a cross-over cable.
I have the sysctl max values set very generous, though the min
and default are fairly small.
This was with kernel 2.6.20.
Was the auto-tuning put in after 2.6.20? If not, has this
been tested through a higher latency link? Or, am I confused
and you are talking about some other setsockopt?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2007-10-12 0:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 23:27 Question on TSO maximum segment sizes Waskiewicz Jr, Peter P
2007-10-11 23:37 ` David Miller
2007-10-11 23:50 ` Rick Jones
2007-10-12 0:02 ` David Miller
2007-10-12 0:06 ` Waskiewicz Jr, Peter P
2007-10-12 0:17 ` Ben Greear [this message]
2007-10-12 0:22 ` David Miller
2007-10-12 1:22 ` John Heffner
2007-10-12 1:29 ` Ben Greear
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=470EBD2C.8020704@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=rick.jones2@hp.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).