From: Rick Jones <rick.jones2@hp.com>
To: netdev@oss.sgi.com
Subject: Re: [PATCH] Super TSO
Date: Thu, 19 May 2005 17:45:56 -0700 [thread overview]
Message-ID: <428D3344.6090107@hp.com> (raw)
In-Reply-To: <200505200015.j4K0FNVG005262@guinness.s2io.com>
> In this case, 64k TSO becomes a liability and it will make sense to limit it.
> TSO "sweet spot" will be captured anyways - at least on fast networks, going
> from 1.5k to 9k typically doubles throughput, while going from 9k to 64k
> adds no more than another 10% (plus a little bit of free %cpu, but not that
> much).
On the surface, that just sounds like something adhering to the laws of
diminishing returns. As you increase the TSO size, you are shrinking the
per-send costs, but the per-byte costs (if there is a copy from user to kernel)
and the ack costs remain the same.
If that 1500 to 9K to 64K is an MTU (and thus real MSS) change than the per-send
and ack costs are what are diminishing but the per-byte costs remain the same.
Asymptotes and all that...
rick jones
prev parent reply other threads:[~2005-05-20 0:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 2:24 [PATCH] Super TSO David S. Miller
2005-05-18 13:43 ` Andi Kleen
2005-05-18 19:57 ` David S. Miller
2005-05-20 0:15 ` Leonid Grossman
2005-05-20 0:21 ` David S. Miller
2005-05-20 0:36 ` Leonid Grossman
2005-05-20 0:55 ` David S. Miller
2005-05-20 1:25 ` Leonid Grossman
2005-05-20 1:28 ` David S. Miller
2005-05-20 0:45 ` Rick Jones [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=428D3344.6090107@hp.com \
--to=rick.jones2@hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.