From: Willy Tarreau <w@1wt.eu>
To: Rick Jones <rick.jones2@hp.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
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 20:43:19 +0100 [thread overview]
Message-ID: <20130110194319.GB16165@1wt.eu> (raw)
In-Reply-To: <50EF0D2D.3040700@hp.com>
On Thu, Jan 10, 2013 at 10:49:17AM -0800, Rick Jones wrote:
> On 01/10/2013 10:42 AM, Eric Dumazet wrote:
> >Can we use zero copy for the sender as well (sendfile() or vmsplice()) ?
>
> Not at present. The TCP_SENDFILE test has not been "migrated" and there
> is no corresponding sendfile() test in the omni code, so the attempt to
> enable copy-avoidance won't "take."
Note that in my httpterm server, I'm using tee+splice(). I had a problem
with vmsplice() in the past, I don't remember which one.
For the "inject" http client, I'm using recv(MSG_TRUNC) which is always
faster than splice() and does the job well, considering that the goal is
to count and destroy data very fast.
By combining them both on the same machine over the loopback, I see
70 Gbps on a core-2 duo 2.66 GHz. These are obviously not real gigs,
but at least it shows what the network stack can do when we remove
memory copies !
Regards,
Willy
next prev parent reply other threads:[~2013-01-10 19:43 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
2013-01-10 18:42 ` Eric Dumazet
2013-01-10 18:49 ` Rick Jones
2013-01-10 19:43 ` Willy Tarreau [this message]
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=20130110194319.GB16165@1wt.eu \
--to=w@1wt.eu \
--cc=c.becker@traviangames.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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).