From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
eric.dumazet@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, ebiederm@xmission.com,
davem@davemloft.net
Subject: [PATCHv2-RFC 0/6] tun zerocopy support
Date: Thu, 17 May 2012 00:15:49 +0300 [thread overview]
Message-ID: <cover.1337202879.git.mst@redhat.com> (raw)
So this still triggers some failures under stress
but I thought it might be helpful to post here
since people expressed interest.
This uses some patches from Ian's patchset
to support zerocopy with tun.
We are still trying to figure out how to make
everything work properly with tcp but tun seems
easier, and it's helpful since not everyone can
use macvtap.
There's some code duplication between tun and macvtap
now: common code could move to net/core/datagram.c,
this patch does not do this yet.
--
MST
Michael S. Tsirkin (6):
skbuff: add an api to orphan frags
skbuff: convert to skb_orphan_frags
skbuff: export skb_copy_ubufs
tun: orphan frags on xmit
net: orphan frags on receive
tun: experimental zero copy tx support
drivers/net/tun.c | 134 ++++++++++++++++++++++++++++++++++++++++++++++--
include/linux/skbuff.h | 16 ++++++
net/core/dev.c | 2 +
net/core/skbuff.c | 24 +++-----
4 files changed, 156 insertions(+), 20 deletions(-)
--
MST
next reply other threads:[~2012-05-16 21:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 21:15 Michael S. Tsirkin [this message]
2012-05-16 21:15 ` [PATCHv2-RFC 1/6] skbuff: add an api to orphan frags Michael S. Tsirkin
2012-05-16 21:16 ` [PATCHv2-RFC 2/6] skbuff: convert to skb_orphan_frags Michael S. Tsirkin
2012-05-16 21:16 ` [PATCHv2-RFC 3/6] skbuff: export skb_copy_ubufs Michael S. Tsirkin
2012-05-16 21:16 ` [PATCHv2-RFC 4/6] tun: orphan frags on xmit Michael S. Tsirkin
2012-05-16 21:16 ` [PATCHv2-RFC 5/6] net: orphan frags on receive Michael S. Tsirkin
2012-05-16 21:16 ` [PATCHv2-RFC 6/6] tun: experimental zero copy tx support Michael S. Tsirkin
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=cover.1337202879.git.mst@redhat.com \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=eric.dumazet@gmail.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).