From: "David S. Miller" <davem@davemloft.net>
To: Rick Jones <rick.jones2@hp.com>
Cc: netdev@oss.sgi.com
Subject: Re: on the wire behaviour of TSO on/off is supposed to be the same yes?
Date: Fri, 21 Jan 2005 14:18:20 -0800 [thread overview]
Message-ID: <20050121141820.7d59a2d1.davem@davemloft.net> (raw)
In-Reply-To: <41F17B7E.2020002@hp.com>
On Fri, 21 Jan 2005 14:00:30 -0800
Rick Jones <rick.jones2@hp.com> wrote:
> Indeed, it waited for the ACK 4335, but then shouldn't it have emitted 4344+1448 or 5792 bytes or perhaps 7240 (since there were two
> ACKs?
The tcp_tso_win_divisor calculation occurs on the congestion window at the
time of the user request, not at the time of the ACK.
That's an interesting observation actually, thanks for showing it.
It means that ideally we might want to try and find a way to either:
1) defer the TSO window size calculation to some later moment, ie.
at tcp_write_xmit() time
2) use an optimistic TSO size calculation at the same moment we compute
it now, and later if it is found to be too aggressive we chop up the
TSO frame and resegment the transmit queue to accomodate
Neither is easy to implement as far as I can tell, but it should fix
all the problems IBM and others are trying to work around by setting
the tcp_tso_win_divisor really small.
next prev parent reply other threads:[~2005-01-21 22:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 19:01 on the wire behaviour of TSO on/off is supposed to be the same yes? Rick Jones
2005-01-21 19:58 ` Jon Mason
2005-01-21 20:18 ` Rick Jones
2005-01-21 20:44 ` David S. Miller
2005-01-21 22:00 ` Rick Jones
2005-01-21 22:18 ` David S. Miller [this message]
2005-01-21 22:48 ` Rick Jones
2005-01-21 22:58 ` Rick Jones
2005-01-22 4:44 ` David S. Miller
2005-01-22 18:58 ` rick jones
2005-01-22 4:49 ` David S. Miller
2005-01-22 19:05 ` rick jones
2005-01-24 20:33 ` Rick Jones
2005-01-24 20:43 ` David S. Miller
2005-01-24 21:22 ` Rick Jones
2005-01-28 0:10 ` Rick Jones
2005-01-28 0:57 ` David S. Miller
2005-01-28 1:36 ` Rick Jones
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=20050121141820.7d59a2d1.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@oss.sgi.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).