From: "David S. Miller" <davem@davemloft.net>
To: Anton Blanchard <anton@samba.org>
Cc: herbert@gondor.apana.org.au, netdev@oss.sgi.com
Subject: Re: some TSO analysis
Date: Thu, 11 Nov 2004 10:26:22 -0800 [thread overview]
Message-ID: <20041111102622.19fb1a22.davem@davemloft.net> (raw)
In-Reply-To: <20041111083647.GA20769@krispykreme.ozlabs.ibm.com>
On Thu, 11 Nov 2004 19:36:47 +1100
Anton Blanchard <anton@samba.org> wrote:
> Im interested if the divisor of 8 was based on some testing, or if we
> can tune the default a bit. It would be nice for TSO to kick in on
> normal workloads (like web serving).
It was the best compromise found between performance and burstyness.
If you set it too small, you get large bursts of TSO created
frames which is very undesirable.
prev parent reply other threads:[~2004-11-11 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 5:06 some TSO analysis Anton Blanchard
2004-11-11 7:20 ` Herbert Xu
2004-11-11 8:36 ` Anton Blanchard
2004-11-11 18:26 ` David S. Miller [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=20041111102622.19fb1a22.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=anton@samba.org \
--cc=herbert@gondor.apana.org.au \
--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).