From: Rusty Russell <rusty@rustcorp.com.au>
To: "netdev" <netdev@vger.kernel.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
"Michael S. Tsirkin" <mst@redhat.com>,
virtualization@lists.linux-foundation.org,
Rusty Russell <rusty@rustcorp.com.au>
Subject: [PATCH 0/3] virtio: simplify virtio_ring.
Date: Wed, 3 Sep 2014 13:59:13 +0930 [thread overview]
Message-ID: <1409718556-3041-1-git-send-email-rusty@rustcorp.com.au> (raw)
I resurrected these patches after prompting from Andy Lutomirski's
recent patches. I put them on the back-burner because vring_bench
had a 15% slowdown on my laptop: pktgen testing revealed a speedup,
if anything, so I've cleaned them up.
Rusty Russell (3):
virtio_net: pass well-formed sgs to virtqueue_add_*()
virtio_ring: assume sgs are always well-formed.
virtio_ring: unify direct/indirect code paths.
drivers/net/virtio_net.c | 5 +-
drivers/virtio/virtio_ring.c | 185 +++++++++++++++----------------------------
2 files changed, 69 insertions(+), 121 deletions(-)
--
1.9.1
next reply other threads:[~2014-09-03 4:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 4:29 Rusty Russell [this message]
2014-09-03 4:29 ` [PATCH 1/3] virtio_net: pass well-formed sgs to virtqueue_add_*() Rusty Russell
2014-09-03 4:54 ` Andy Lutomirski
2014-09-03 10:23 ` Jesper Dangaard Brouer
2014-09-03 4:29 ` [PATCH 2/3] virtio_ring: assume sgs are always well-formed Rusty Russell
2014-09-03 4:29 ` [PATCH 3/3] virtio_ring: unify direct/indirect code paths Rusty Russell
2014-09-04 1:59 ` Andy Lutomirski
2014-09-05 2:55 ` Rusty Russell
2014-09-05 10:55 ` Paolo Bonzini
2014-09-08 17:32 ` Andy Lutomirski
[not found] ` <1409718556-3041-2-git-send-email-rusty__16380.2289790057$1409718628$gmane$org@rustcorp.com.au>
2014-09-05 10:40 ` [PATCH 1/3] virtio_net: pass well-formed sgs to virtqueue_add_*() Paolo Bonzini
2014-09-07 7:20 ` Michael S. Tsirkin
2014-10-14 2:21 ` Rusty Russell
2014-09-05 21:27 ` [PATCH 0/3] virtio: simplify virtio_ring 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=1409718556-3041-1-git-send-email-rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=luto@amacapital.net \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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).