From: Anton Blanchard <anton@samba.org>
To: "David S. Miller" <davem@redhat.com>
Cc: davidm@hpl.hp.com, davidm@napali.hpl.hp.com,
scott.feldman@intel.com, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com
Subject: Re: [patch] e1000 TSO parameter
Date: Tue, 29 Jul 2003 16:53:07 +1000 [thread overview]
Message-ID: <20030729065307.GC13227@krispykreme> (raw)
In-Reply-To: <20030714223822.23b78f9b.davem@redhat.com>
Hi,
> > So we get almost 15% of throughput drop. This was with plain "netkit
> > fptd". AFAIK, it does a simple read/write loop (not sendfile()).
We've been seeing rather variable results for TSO as well. With TSO off
netperf TCP_STREAM will hit line speed and stay there. With TSO on
some runs will hit line speed and others will be about 100Mbit/sec
slower.
> When we use TSO for non-sendfile() applications it really
> stresses memory allocations. We do these 64K+ kmalloc()'s
> for each packet we construct.
Yep we definitely noticed much more higher allocations when watching
/proc/slab. Playing around with slab tuning didnt seem to help.
Anton
next prev parent reply other threads:[~2003-07-29 6:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 4:42 [patch] e1000 TSO parameter Feldman, Scott
2003-07-15 4:45 ` David S. Miller
2003-07-15 4:57 ` David Mosberger
2003-07-15 5:31 ` David Mosberger
2003-07-15 5:38 ` David S. Miller
2003-07-15 23:01 ` David Mosberger
2003-07-16 1:39 ` David S. Miller
2003-07-16 6:32 ` David Mosberger
2003-07-16 6:30 ` David S. Miller
2003-07-29 6:53 ` Anton Blanchard [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-15 5:11 Feldman, Scott
2003-07-16 0:27 Feldman, Scott
2003-07-16 0:41 ` David Mosberger
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=20030729065307.GC13227@krispykreme \
--to=anton@samba.org \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=davidm@napali.hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.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.