From: Jeremy Kerr <jeremy@redfishsoftware.com.au>
To: netdev@oss.sgi.com
Cc: anton@au.ibm.com
Subject: Reenabling TSO
Date: Mon, 8 Mar 2004 15:32:02 +1100 [thread overview]
Message-ID: <200403081532.02830.jeremy@redfishsoftware.com.au> (raw)
Hi all,
I've been running a few tests on the TSO & e1000 code which involve stressing
a link between two hosts. The test program is rather trivial, simply repeated
calls to sendfile() over a socket. The problem occurs when we see a TCP
retransmit on the connection, after which TSO is disabled.
After looking through tcp_{input,output}.c, there seems to be no code to
reenable TSO - so one retransmit will permanently disable TSO for a socket.
This isn't such a problem for short-lived connections, but longer-lived ones
will only use TSO for a small proportion of the data transferred, depending
on the frequency of retransmits.
So, two questions:
Is it practical to reenable TSO at all?
and
What metric do we use to determine when it is safe to reenable TSO? A simple
metric may be the TCP window size - when this reaches a predefined threshold,
we can set the flag again. However, something more complex involving the
number of sent packets and number of retransmits may be required.
Any thoughts?
Jeremy
reply other threads:[~2004-03-08 4:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200403081532.02830.jeremy@redfishsoftware.com.au \
--to=jeremy@redfishsoftware.com.au \
--cc=anton@au.ibm.com \
--cc=netdev@oss.sgi.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).