From: Rick Jones <rick.jones2@hp.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Willy Tarreau <w@1wt.eu>,
Christian Becker <c.becker@traviangames.com>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: tainted warnings with tcp splicing in 3.7.1
Date: Thu, 10 Jan 2013 10:22:21 -0800 [thread overview]
Message-ID: <50EF06DD.7070207@hp.com> (raw)
In-Reply-To: <1357834825.27446.2205.camel@edumazet-glaptop>
On 01/10/2013 08:20 AM, Eric Dumazet wrote:
> I also want to thanks Rick, as the latest netperf has splice() support.
>
> Thanks Rick !
You are quite welcome - and thank you for helping me get it to actually
work :)
Those wishing to try it themselves should grab the top-of-trunk netperf
bits from http://www.netperf.org/svn/netperf2/trunk . The use of
splice() is gated by a test-specific -V option:
raj@tardy:~/netperf2_trunk/src$ ./netperf -t omni -- -d recv -V
OMNI Receive TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
localhost.localdomain () port 0 AF_INET : copy avoidance : demo
Remote Local Remote Elapsed Throughput Throughput
Send Socket Recv Socket Send Time Units
Size Size Size (sec)
Final Final
1661688 4194304 16384 10.00 26103.14 10^6bits/s
You should see that "copy avoidance" appearing in the test banner. It
will also "take" for things like a migrated TCP_mumble test. For those
cases where you don't see a throughput change, enabling CPU utilization
measurement and looking at that and service demand should show a difference.
happy benchmarking,
rick jones
next prev parent reply other threads:[~2013-01-10 18:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 13:01 tainted warnings with tcp splicing in 3.7.1 Christian Becker
2013-01-09 14:50 ` Lukas Tribus
2013-01-09 17:01 ` Eric Dumazet
2013-01-09 17:09 ` Eric Dumazet
2013-01-10 6:59 ` Eric Dumazet
2013-01-10 7:21 ` Willy Tarreau
2013-01-10 15:29 ` Eric Dumazet
2013-01-10 16:20 ` Eric Dumazet
2013-01-10 18:22 ` Rick Jones [this message]
2013-01-10 18:42 ` Eric Dumazet
2013-01-10 18:49 ` Rick Jones
2013-01-10 19:43 ` Willy Tarreau
2013-01-12 0:46 ` [PATCH net-next] net: splice: fix __splice_segment() Eric Dumazet
2013-01-12 0:48 ` David Miller
2013-01-10 18:27 ` tainted warnings with tcp splicing in 3.7.1 Lukas Tribus
2013-01-10 18:37 ` Eric Dumazet
2013-01-10 22:39 ` David Miller
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=50EF06DD.7070207@hp.com \
--to=rick.jones2@hp.com \
--cc=c.becker@traviangames.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=w@1wt.eu \
/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).