From: David Miller <davem@davemloft.net>
To: greearb@candelatech.com
Cc: peter.p.waskiewicz.jr@intel.com, rick.jones2@hp.com,
netdev@vger.kernel.org
Subject: Re: Question on TSO maximum segment sizes.
Date: Thu, 11 Oct 2007 17:22:09 -0700 (PDT) [thread overview]
Message-ID: <20071011.172209.26285198.davem@davemloft.net> (raw)
In-Reply-To: <470EBD2C.8020704@candelatech.com>
From: Ben Greear <greearb@candelatech.com>
Date: Thu, 11 Oct 2007 17:17:48 -0700
> 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?
It's been there for quite some time.
next prev parent reply other threads:[~2007-10-12 0:22 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
2007-10-12 0:22 ` David Miller [this message]
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=20071011.172209.26285198.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=greearb@candelatech.com \
--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).